search for: trylatency

Hello Everyone, I am running Dovecot 2.0.15 with its Sieve plug-in, and Roundcube 0.5.3. I have a problem with just one particular user, who after creating a filters set and creating a filter in Roundcube, this user cannot activate the filters set. At first, this user could not create a filter at all. That was resolved by creating the "sieve" directory with the right permissions in

Thank you Steffen Kaiser. I enabled the auth_debug and saw this error for permissions: Aug 22 13:41:44 managesieve($u): Error: sieve-storage: Creating symlink() /home/$u/.dovecot.sieve to sieve/Out of office.sieve failed: Permission denied The user's home directory was owned by root. Can not explain it why it was so. Thanks again! > On Wed, 21 Aug 2013, Joe Lourenco wrote: > >

...easing the max pressure of the entire region.    if (DAG->isTrackingPressure() && tryPressure(TryCand.RPDelta.CurrentMax,         Cand.RPDelta.CurrentMax, TryCand, Cand, RegMax, TRI, DAG->MF))      return;    /// INSERTION POINT    ... } I had started to experiment with adding tryLatency() in various places, and found this to be the best spot for SystemZ/SPEC-2006. This gave noticeable improvements immediately that were to good to ignore, so I started figuring out things about the regressions that of course also showed up. Eventually I have come up after many iterations a combi...

Hello, On a dovecot 2.0.14 proxy, I found that proxying managesieve works well when using 'starttls' option in pass_attrs, but does not work when using 'ssl' option. The backend server is also dovecot 2.0.14; when using the ssl option, it reports "no auth attempts" in the logs about managesieve-login, and meanwhile the MUA, Thunderbird with sieve plugin, reports

...that are acyclic path limited, aggressively schedule for // latency. This can result in very long dependence chains scheduled in // sequence, so once every cycle (when CurrMOps == 0), switch to normal // heuristics. if (Rem.IsAcyclicLatencyLimited && !Zone->getCurrMOps() && tryLatency(TryCand, Cand, *Zone)) return; Is this an error in comment or code? The CurrMOps is 0 once per cycle, which means this is actually done once per cycle, in contrast to what the comment suggests. ... // Schedule aggressively for latency in PostRA mode. We don't check for // acycl...

Hi Andy, Thanks for the explanations. Yes AMDGPU is in-order and has MicroOpBufferSize = 1. Re "issue limited" and instruction groups: could it make sense to disable the generic scheduler's detection of issue limitation on in-order CPUs, or on CPUs that don't define instruction groups, or some similar condition? Something like: --- a/lib/CodeGen/MachineScheduler.cpp +++

Hello dovecot users, I have updated the MANAGESIEVE patch to (hopefully) fix the compilation issues reported by Robin Breathe. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to significant changes in the master code. Change Log V6 ------------- - Corked the client output stream while producing the capability greeting and on other some