From: Goswin von Brederlow <goswin-v-b@web.de>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: goswin-v-b@web.de, linux-kernel@vger.kernel.org
Subject: Re: include/linux/aio_abi.h and IOCB_CMD_POLL
Date: Thu, 04 Jun 2009 17:18:24 +0200 [thread overview]
Message-ID: <87hbyw6n9b.fsf@frosties.localdomain> (raw)
In-Reply-To: <E1MCCnb-0005Bc-09@pomaz-ex.szeredi.hu> (Miklos Szeredi's message of "Thu, 04 Jun 2009 15:16:03 +0200")
Miklos Szeredi <miklos@szeredi.hu> writes:
> On Thu, 04 Jun 2009, Goswin von Brederlow wrote:
>> 3) Are there any alternatives to libaio that don't use threads and
>> support polling?
>
> There are the poll, select and epoll interfaces that block, but are
> able to multiplex events from many file descriptors.
Unfortunately libaio does not use an fd to pass events between user
and kernel space so one can't use poll, select or epoll to wait for
/dev/fuse or libaio to have some work pending. And none of them
replace libaio functionality in respect to read/write.
And alternating between io_getevents and e.g. select with a tiny
timeout seems like a verry bad idea efficiency wise.
> And there's the O_ASYNC flag that can be set with an fcntl(), that
> sends a SIGIO signal on an I/O event.
This might work together with libaio. Never used SIGIO though but I
will try. Thanks for the idea.
> All of these work on /dev/fuse.
>
> Thanks,
> Miklos
MfG
Goswin
next prev parent reply other threads:[~2009-06-04 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 23:18 Goswin von Brederlow
2009-06-04 13:16 ` Miklos Szeredi
2009-06-04 15:18 ` Goswin von Brederlow [this message]
2009-06-04 15:19 ` Davide Libenzi
2009-06-04 22:53 ` Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hbyw6n9b.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®