search for: iterateable

Displaying 14 results from an estimated 14 matches for "iterateable".

Did you mean: iteratable
2020 Mar 19
1
Quota plugin and director
In data gioved? 19 marzo 2020 09:10:06 CET, Aki Tuomi ha scritto: > If you are using director, you can issue `doveadm quota recalc -A` on > director, which will then direct it to correct backend. > > For this to work, it requires that you setup doveadm server on the backend, > and configure doveadm_port and doveadm_password on director. It also either > needs iteratable user
2020 Mar 19
2
Quota plugin and director
In data mercoled? 18 marzo 2020 23:08:27 CET, Alessio Cecchi ha scritto: > Ciao Simone, > > why you want each backend to recalc quota only for its managed users and > not run "doveadm quota recalc -A" only one time from a backend tha > recalc quota for all users? > Because the indexes are local to the backends. If I make the recalc from one backend only, that one
2017 Jul 07
2
how to make user iteration work (with active directory ldap)
We received no replies to this email that we sent a few days ago. We're not sure why. If we miss something that is obvious to everybody, kindly point it out. We ?ould like to get iteration working, to be able to mass-delete specific emails from all mailboxes, in case of for example received virusses... Here is my question again: Hi, User iteration doesn't work, we're getting:
2013 Sep 19
0
[LLVMdev] Experimental Evaluation of the Schedulers in LLVM 3.3
On 17.09.2013, at 20:04, Ghassan Shobaki <ghassan_shobaki at yahoo.com> wrote: > Hi Andy, > > We have done some experimental evaluation of the different schedulers in LLVM 3.3 (source, BURR, ILP, fast, MI). The evaluation was done on x86-64 using SPEC CPU2006. We have measured both the amount of spill code as well as the execution time as detailed below. > > Here are our
2015 Mar 28
2
[LLVMdev] LLVMContextImpl.h not installed?
Hi all, I 'd like to fetch a list of structures, and found that it could be done via LLVMContextImpl *pImpl = Context.pImpl; pImpl->AnonStructTypes This however needs the inclusion of LLVMContextImpl.h, which is not contained in the includes dir, but in the lib/IR dir (next to the .cpp files) and is not installed under /usr/local/include... Whats the reason for this? Isn't it
2017 Jul 07
0
how to make user iteration work (with active directory ldap)
On 07.07.2017 10:33, mj wrote: > We received no replies to this email that we sent a few days ago. > We're not sure why. If we miss something that is obvious to everybody, > kindly point it out. > We ?ould like to get iteration working, to be able to mass-delete > specific emails from all mailboxes, in case of for example received > virusses... > > Here is my question
2020 Mar 19
0
Quota plugin and director
> On 19/03/2020 10:06 Simone Lazzaris <simone.lazzaris at qcom.it> wrote: > > > > In data mercoled? 18 marzo 2020 23:08:27 CET, Alessio Cecchi ha scritto: > > > Ciao Simone, > > > > > > why you want each backend to recalc quota only for its managed users and > > > not run "doveadm quota recalc -A" only one time from a
2013 Sep 19
1
[LLVMdev] Experimental Evaluation of the Schedulers in LLVM 3.3
Our test machine has two Intel Xeon E5540 processors running at 2.53 GHz with 24 GB of memory. Each CPU has 8 threads (16 threads in total). All our tests, however, were single threaded. Which result is particularly surprising for you? The low impact of the MI scheduler, the relatively good performance of the source scheduler or the relatively poor performance of the ILP scheduler? Thanks
2023 Mar 13
1
[PATCH drm-next v2 05/16] drm: manager to keep track of GPUs VA mappings
On 3/7/23 23:43, Liam R. Howlett wrote: > * Danilo Krummrich <dakr at redhat.com> [230306 10:46]: >> On 3/2/23 03:38, Liam R. Howlett wrote: >>> * Danilo Krummrich <dakr at redhat.com> [230227 08:17]: >>> >>> ... >>>>>> Would this variant be significantly more efficient? >>>>> >>>>> Well, what you are
2013 Sep 17
11
[LLVMdev] Experimental Evaluation of the Schedulers in LLVM 3.3
Hi Andy, We have done some experimental evaluation of the different schedulers in LLVM 3.3 (source, BURR, ILP, fast, MI). The evaluation was done on x86-64 using SPEC CPU2006. We have measured both the amount of spill code as well as the execution time as detailed below. Here are our main findings: 1. The SD schedulers significantly impact the spill counts and the execution times for many
2013 Jul 12
0
[LLVMdev] MI Scheduler vs SD Scheduler?
On Jul 2, 2013, at 2:35 PM, Ghassan Shobaki <ghassan_shobaki at yahoo.com> wrote: > Thank you for the answers! We are currently trying to test the MI scheduler. We are using LLVM 3.3 with Dragon Egg 3.3 on an x86-64 machine. So far, we have run one SPEC CPU2006 test with the MI scheduler enabled using the option -fplugin-arg-dragonegg-llvm-option='-enable-misched:true' with -O3.
2023 Mar 06
2
[PATCH drm-next v2 05/16] drm: manager to keep track of GPUs VA mappings
On 3/2/23 03:38, Liam R. Howlett wrote: > * Danilo Krummrich <dakr at redhat.com> [230227 08:17]: > > ... >>>> Would this variant be significantly more efficient? >>> >>> Well, what you are doing is walking the tree to see if there's anything >>> there... then re-walking the tree to store it. So, yes, it's much more >>>
2023 Feb 27
2
[PATCH drm-next v2 05/16] drm: manager to keep track of GPUs VA mappings
On 2/23/23 20:09, Liam R. Howlett wrote: > * Danilo Krummrich <dakr at redhat.com> [230222 13:13]: >> On 2/21/23 19:20, Liam R. Howlett wrote: >>> * Danilo Krummrich <dakr at redhat.com> [230217 08:45]: >>>> Add infrastructure to keep track of GPU virtual address (VA) mappings >>>> with a decicated VA space manager implementation.
2013 Jul 02
2
[LLVMdev] MI Scheduler vs SD Scheduler?
Thank you for the answers! We are currently trying to test the MI scheduler. We are using LLVM 3.3 with Dragon Egg 3.3 on an x86-64 machine. So far, we have run one SPEC CPU2006 test with the MI scheduler enabled using the option -fplugin-arg-dragonegg-llvm-option='-enable-misched:true' with -O3. This enables the machine scheduler in addition to the SD scheduler. We have verified this by