Is it possible to block pending queued RealTime signals (AIO originating)?
Garrett Cooper
yanegomi at gmail.com
Tue Jan 8 17:40:39 UTC 2013
On Jan 8, 2013, at 9:20 AM, Adrian Chadd <adrian at freebsd.org> wrote:
> On 8 January 2013 08:15, Richard Sharpe <rsharpe at richardsharpe.com> wrote:
>> 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.
>
> Embrace FreeBSD's nice asynchronous APIs for doing things! You know you want to!
>
> (Then, convert parts of samba over to use grand central dispatch... :-)
>
> Seriously though - I was doing network/disk IO using real time signals
> what, 10 + years ago on Linux and it plain sucked. AIO + kqueue +
> waitcomplete is just brilliant. kqueue for signal delivery is also
> just brilliant. Just saying.
Or just use libevent to abstract away kqueues/inotify/etc? Samba isn't just for freebsd...
Thanks,
-Garrett
More information about the freebsd-hackers
mailing list