From: Ingo Molnar <mingo@elte.hu>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: David Miller <davem@davemloft.net>,
Ulrich Drepper <drepper@redhat.com>,
Andrew Morton <akpm@osdl.org>, netdev <netdev@vger.kernel.org>,
Zach Brown <zach.brown@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
Chase Venters <chase.venters@clientec.com>,
Johann Borck <johann.borck@densedata.com>,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Jamal Hadi Salim <hadi@cyberus.ca>
Subject: Re: [take29 0/8] kevent: Generic event handling mechanism.
Date: Fri, 29 Dec 2006 14:24:39 +0100 [thread overview]
Message-ID: <20061229132439.GA30005@elte.hu> (raw)
In-Reply-To: <20061229131452.GA5641@2ka.mipt.ru>
* Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> > (rarer things like mouse/input events can stay with poll
> > notifications)
> >
> > and it is /especially/ important to include block IO events in
> > kevents to be able to judge its performance and scalability relative
> > to the async IO API and infrastructure.
>
> Yes, async IO is a significant part, and will be implemented, IMHO,
> new design I highlighted in linux-fsdevel@ in AIO related thread is
> the way to go (at least I will imlement it that way).
yes. Note that a prototype exists already: take a look at Tux's "work
atom" infrastructure of how you can build a relatively straightforward
state-machine that can be programmed and can be driven even from IRQ
contexts. Via that i implemented fully asynchronous IO for networking 5
years ago, and programmed it to handle HTTP and FTP protocol server
logic, fully asynchronously. (For block IO it also does emulation of
event handling via the 'cachemiss' kernel threads. State-machine driven
filesystems are quite hard - but not impossible in the long run.)
It would be a natural thing to extend that fundamental concept to
user-space as well. /That/ i'd call a generic, grounds-up event handling
infrastructure. That would be a worthwile unification point for all
existing IO APIs.
Ingo
next prev parent reply other threads:[~2006-12-29 13:24 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3154985aa0591036@2ka.mipt.ru>
2006-12-17 13:53 ` [take28-resend_2->0 0/8] kevent: Generic event handling mechanism Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 1/8] kevent: Description Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 2/8] kevent: Core files Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 3/8] kevent: poll/select() notifications Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 4/8] kevent: Socket notifications Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 5/8] kevent: Timer notifications Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 6/8] kevent: Pipe notifications Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 7/8] kevent: Signal notifications Evgeniy Polyakov
2006-12-17 13:53 ` [take28-resend_2->0 8/8] kevent: Kevent posix timer notifications Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 0/8] kevent: Generic event handling mechanism Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 1/8] kevent: Description Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 2/8] kevent: Core files Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 3/8] kevent: poll/select() notifications Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 4/8] kevent: Socket notifications Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 5/8] kevent: Timer notifications Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 6/8] kevent: Pipe notifications Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 7/8] kevent: Signal notifications Evgeniy Polyakov
2006-12-21 9:14 ` [take28-resend_1->0 8/8] kevent: Kevent posix timer notifications Evgeniy Polyakov
2006-12-21 10:35 ` [take28-resend_1->0 0/8] kevent: Generic event handling mechanism Evgeniy Polyakov
2006-12-21 10:41 ` Jeff Garzik
2006-12-21 10:49 ` Evgeniy Polyakov
2006-12-21 10:57 ` Evgeniy Polyakov
2006-12-21 13:48 ` jamal
2006-12-21 14:04 ` Evgeniy Polyakov
2006-12-21 14:21 ` jamal
2006-12-21 14:23 ` Evgeniy Polyakov
2006-12-21 14:36 ` Evgeniy Polyakov
2006-12-21 14:40 ` jamal
2006-12-21 14:46 ` Evgeniy Polyakov
2006-12-21 16:42 ` jamal
2006-12-21 16:51 ` Evgeniy Polyakov
2006-12-23 16:51 ` [take29 " Evgeniy Polyakov
2006-12-23 16:51 ` [take29 1/8] kevent: Description Evgeniy Polyakov
2006-12-23 16:51 ` [take29 2/8] kevent: Core files Evgeniy Polyakov
2006-12-23 16:51 ` [take29 3/8] kevent: poll/select() notifications Evgeniy Polyakov
2006-12-23 16:51 ` [take29 4/8] kevent: Socket notifications Evgeniy Polyakov
2006-12-23 16:51 ` [take29 5/8] kevent: Timer notifications Evgeniy Polyakov
2006-12-23 16:51 ` [take29 6/8] kevent: Pipe notifications Evgeniy Polyakov
2006-12-23 16:51 ` [take29 7/8] kevent: Signal notifications Evgeniy Polyakov
2006-12-23 16:51 ` [take29 8/8] kevent: Kevent posix timer notifications Evgeniy Polyakov
2006-12-23 17:10 ` [take29 0/8] kevent: Generic event handling mechanism Evgeniy Polyakov
2006-12-28 15:56 ` Ingo Molnar
2006-12-29 8:48 ` Evgeniy Polyakov
2006-12-28 16:01 ` Ingo Molnar
2006-12-29 8:55 ` Evgeniy Polyakov
2006-12-29 12:54 ` Ingo Molnar
2006-12-29 13:14 ` Evgeniy Polyakov
2006-12-29 13:24 ` Ingo Molnar [this message]
2006-12-29 12:25 ` [take30 0/9] " Evgeniy Polyakov
2006-12-29 12:25 ` [take30 1/9] kevent: Description Evgeniy Polyakov
2006-12-29 12:25 ` [take30 2/9] kevent: Core files Evgeniy Polyakov
2006-12-29 12:25 ` [take30 3/9] kevent: poll/select() notifications Evgeniy Polyakov
2006-12-29 12:25 ` [take30 4/9] kevent: Socket notifications Evgeniy Polyakov
2006-12-29 12:25 ` [take30 5/9] kevent: Timer notifications Evgeniy Polyakov
2006-12-29 12:25 ` [take30 6/9] kevent: Pipe notifications Evgeniy Polyakov
2006-12-29 12:25 ` [take30 7/9] kevent: Signal notifications Evgeniy Polyakov
2006-12-29 12:25 ` [take30 8/9] kevent: Kevent posix timer notifications Evgeniy Polyakov
2006-12-29 12:25 ` [take30 9/9] kevent: Private userspace notifications Evgeniy Polyakov
2007-01-08 19:25 ` [take31 0/10] kevent: Generic event handling mechanism Evgeniy Polyakov
2007-01-08 19:25 ` [take31 1/10] kevent: Description Evgeniy Polyakov
2007-01-08 19:25 ` [take31 2/10] kevent: Core files Evgeniy Polyakov
2007-01-08 19:25 ` [take31 3/10] kevent: poll/select() notifications Evgeniy Polyakov
2007-01-08 19:25 ` [take31 4/10] kevent: Socket notifications Evgeniy Polyakov
2007-01-08 19:25 ` [take31 5/10] kevent: Timer notifications Evgeniy Polyakov
2007-01-08 19:25 ` [take31 6/10] kevent: Pipe notifications Evgeniy Polyakov
2007-01-08 19:25 ` [take31 7/10] kevent: Signal notifications Evgeniy Polyakov
2007-01-08 19:26 ` [take31 8/10] kevent: Kevent posix timer notifications Evgeniy Polyakov
2007-01-08 19:26 ` [take31 9/10] kevent: Private userspace notifications Evgeniy Polyakov
2007-01-08 19:26 ` [take31 10/10] kevent: Kevent based AIO (aio_sendfile()) Evgeniy Polyakov
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=20061229132439.GA30005@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=chase.venters@clientec.com \
--cc=davem@davemloft.net \
--cc=drepper@redhat.com \
--cc=hadi@cyberus.ca \
--cc=hch@infradead.org \
--cc=jeff@garzik.org \
--cc=johann.borck@densedata.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).