Date: Tue, 08 Jan 2013 08:15:55 -0800 From: Richard Sharpe <rsharpe@richardsharpe.com> To: Adrian Chadd <adrian@freebsd.org> Cc: Daniel Eischen <deischen@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: Is it possible to block pending queued RealTime signals (AIO originating)? Message-ID: <1357661755.6752.32.camel@localhost.localdomain> In-Reply-To: <CAJ-VmomN5G70ftbV-uETYwUV7U6zLq%2BUKdav%2BM_B9HYB7HuEpQ@mail.gmail.com> References: <1357608470.6752.22.camel@localhost.localdomain> <Pine.GSO.4.64.1301072215400.14726@sea.ntplx.net> <1357626412.6752.24.camel@localhost.localdomain> <CAJ-VmomN5G70ftbV-uETYwUV7U6zLq%2BUKdav%2BM_B9HYB7HuEpQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2013-01-08 at 07:36 -0800, Adrian Chadd wrote: > .. or you could abstract it out a bit and use freebsd's > aio_waitcomplete() or kqueue aio notification. > > It'll then behave much saner. Yes, going forward that is what I want to do ... this would work nicely with a kqueue back-end for Samba's tevent subsystem, and if someone has not already written such a back end, I will have to do so, I guess.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1357661755.6752.32.camel>