search for: postpone

...ile back about postponing vectorization until the linking stage. It seems to me that there could be an advantage to postponing (some) passes until the linking stage, where the entire graph is available. In general, what do people think about the idea of a different flow of LTO where more passes are postponed until the linking stage? Daniel Stewart -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/201409...

Hi, is there any way, based on userdb/passwdb attribute, how to postpone an email delivery? The purpose is, I need to freeze an account (Maildir++) for a few minutes and new email must not be delivered. But emails must be delivered when account is unfrozen. I found few things about Postfix filters, but I'm not sure it's a good way. Thank you, Milo

Hi folks, Due to the Cambridge LLVM Day being today, we're postponing the LLVM Social. It'll initially be next week, but if enough people reply negatively, we can postpone for two weeks from now. Just let me know... cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131118/fe113842/attachment.html>

We delivering packets to monitoring devices, before to check if the virtqueue has enough space. If the virtqueue is full, the transmitting packet is queued up and it will be sent in the next iteration. This causes the same packet to be delivered multiple times to monitoring devices. This patch fixes this issue, postponing the packet delivery to monitoring devices, only when it is properly queued

We delivering packets to monitoring devices, before to check if the virtqueue has enough space. If the virtqueue is full, the transmitting packet is queued up and it will be sent in the next iteration. This causes the same packet to be delivered multiple times to monitoring devices. This patch fixes this issue, postponing the packet delivery to monitoring devices, only when it is properly queued

...ones that don't do post-auth privsep. It also occurs when sshd logs to stderr (eg running under daemontools) or when you have a /dev/log in the privsep chroot. The patch below attempts to solve this for the general case. The idea is that everything is logged by the monitor, except for "postponed" authentications. (The monitor never knows about the "postponed" ones since the slave is just waiting for a response from the client. I don't think it's worth another monitor call to log those.) Index: auth.c ================================================================...

On Tue, Apr 21, 2020 at 11:25:27AM +0200, Stefano Garzarella wrote: > We delivering packets to monitoring devices, before to check if > the virtqueue has enough space. "We [are] delivering packets" and "before to check" -> "before checking". Perhaps it can be rewritten as: Packets are delivered to monitoring devices before checking if the virtqueue has

On Tue, Apr 21, 2020 at 06:17:24PM +0200, Stefano Garzarella wrote: > On Tue, Apr 21, 2020 at 04:42:46PM +0100, Stefan Hajnoczi wrote: > > On Tue, Apr 21, 2020 at 11:25:27AM +0200, Stefano Garzarella wrote: > > > We delivering packets to monitoring devices, before to check if > > > the virtqueue has enough space. > > > > "We [are] delivering

* Miloslav H?la <miloslav.hula at gmail.com> 2015.04.29 22:47: > is there any way, based on userdb/passwdb attribute, how to postpone an > email delivery? The purpose is, I need to freeze an account (Maildir++) for > a few minutes and new email must not be delivered. But emails must be > delivered when account is unfrozen. You can put the messages on hold and then release them again: http://wiki2.dovecot.org/Migration/...

On Tue, Apr 21, 2020 at 04:42:46PM +0100, Stefan Hajnoczi wrote: > On Tue, Apr 21, 2020 at 11:25:27AM +0200, Stefano Garzarella wrote: > > We delivering packets to monitoring devices, before to check if > > the virtqueue has enough space. > > "We [are] delivering packets" and "before to check" -> "before > checking". Perhaps it can be

On Tue, Apr 21, 2020 at 04:42:46PM +0100, Stefan Hajnoczi wrote: > On Tue, Apr 21, 2020 at 11:25:27AM +0200, Stefano Garzarella wrote: > > We delivering packets to monitoring devices, before to check if > > the virtqueue has enough space. > > "We [are] delivering packets" and "before to check" -> "before > checking". Perhaps it can be

...see if there is any > potential benefit. I have attached the patch I used to do the tests, in > case anyone is interested. > > > > Briefly, the patch allows two different flows, with either a flag of > –lto-new or –lto-new2. In the first case, the vectorization passes are > postponed from the end of populateModulePassManager() function to midway > through the addLTOOptimizationPasses(). In the second case, essentially the > entire populateModulePassManager() function is deferred until link time. > > > > I ran spec2000/2006 on an ARM platform (Nexus 4), compar...

Hi people, I got Centos 4.3 on a 1GB Pentium IV machine. The output of free ------------------- $ free total used free shared buffers cached Mem: 1026896 573848 453048 0 2988 131712 -/+ buffers/cache: 439148 587748 Swap: 1052248 137568 914680 ------------------ There is plenty of free ram, but the kernel

Hi all, I'm curious. If I do yum update (which include kernel update) but don't reboot. Is it OK? I mean apart of the kernel, other things like services, we don't have to reboot if we don't have the chance to do it (postponing to some other date), right? Thank you.

100% reproducible. User is using alpine to write an email. Continue postponed composition (answering "No" won't erase it)? y -> [>Empty folder! No messages really postponed!<] Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs Setup: ====== http://wiki2.dovecot.org/HowTo/ImapcProxy coredump available for further...

Hi llvm-dev We have not been able to complete all the work we need to do before merging F18 into LLVM as Flang so we will not be dong that today as previously announced. We propose to slip this back a week to let us finish off the last bits of work. All code changes are in review as of Friday. If you want more detail, you can see the exact status here:

...C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:670:in `block in checking_for'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:276:in `block (2 levels) in postpo ne'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:250:in `open'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:276:in `block in postpone'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:250:in `open'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:272:in `postpone'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:669:in `checking_for'' from C:/Ruby19/lib/ruby/1.9.1/mkmf.rb:720:in `have_library'...

Hi, I have a detailed question about ordered data writes. Suppose we (i.e. intermezzo) does a transaction, which is closed and then followed by an ordered write. Let's assume the ordered write doesn't require new allocation metadata. Is the write still postponed until the first transaction has committed? As far as I can see, prepare_write always starts a transaction, but I'm not sure that this ultimately results in an ordering constraint. - Peter -

...LO16 relocation to calculate R_MIPS_HI16 one because R_MIPS_HI16 uses combined addend (AHI << 16) + (short)ALO where AHI is original R_MIPS_HI16 addend and ALO is addend of the matching R_MIPS_LO16 relocation [1]. There are two methods to do matching and R_MIPS_HI16 calculation. Method A: 1. Postpone R_MIPS_HI16 relocation calculation and record its arguments. 2. When R_MIPS_LO16 is found, iterate over recorded R_MIPS_HI16 relocations, calculate combined addend and apply relocations. 3. At the end check orphaned (without R_MIPS_LO16 pair) R_MIPS_HI16 relocations, show warnings and apply them wi...

Hello, I am running into this error: /Maximum number of connections from user+IP exceeded (mail_max_userip_connections=10)/ The suggested solution in hundreds of support requests on this mailing list and throughout the internet is to increase the number of maximum userip connections. But this is not curing the problem, it is just postponing it to the moment when the new limit is reached. When i