From: Benjamin LaHaise <bcrl@kvack.org>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [1/4] kevent: core files.
Date: Fri, 23 Jun 2006 17:31:44 -0400 [thread overview]
Message-ID: <20060623213144.GF14126@kvack.org> (raw)
In-Reply-To: <20060623210826.GC26168@2ka.mipt.ru>
On Sat, Jun 24, 2006 at 01:08:27AM +0400, Evgeniy Polyakov wrote:
> On Fri, Jun 23, 2006 at 04:44:42PM -0400, Benjamin LaHaise (bcrl@kvack.org) wrote:
> > > AIO completion approach was designed to be used with process context VFS
> > > update. read/write approach can not cover other types of notifications,
> > > like inode updates or timers.
> >
> > The completion event is 100% generic and does not need to come from process
> > context. Calling aio_complete() from irq context is entirely valid.
>
> put_ioctx() can sleep.
Err, no, that should definately not be the case. If it can, someone has
completely broken aio.
> It is not syscall, but overall design should be analyzed.
> It is possible to use existing ssycalls, kevent design does not care
> about how it's data structures are delivered to the internal
> "processor".
Okay, that's good to hear. =-)
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2006-06-23 21:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 17:14 [1/1] Kevent subsystem Evgeniy Polyakov
2006-06-22 19:01 ` James Morris
2006-06-23 5:54 ` Evgeniy Polyakov
2006-06-22 19:53 ` Robert Iakobashvili
2006-06-23 5:50 ` Evgeniy Polyakov
2006-06-23 6:12 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-23 6:14 ` David Miller
2006-06-23 6:18 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-23 7:09 ` [1/4] kevent: core files Evgeniy Polyakov
2006-06-23 18:44 ` Benjamin LaHaise
2006-06-23 19:24 ` Evgeniy Polyakov
2006-06-23 19:55 ` Benjamin LaHaise
2006-06-23 20:17 ` Evgeniy Polyakov
2006-06-23 20:44 ` Benjamin LaHaise
2006-06-23 21:08 ` Evgeniy Polyakov
2006-06-23 21:31 ` Benjamin LaHaise [this message]
2006-06-23 21:43 ` Evgeniy Polyakov
2006-06-23 20:19 ` David Miller
2006-06-23 20:31 ` Benjamin LaHaise
2006-06-23 20:54 ` Evgeniy Polyakov
2006-06-24 9:14 ` Robert Iakobashvili
2006-06-23 20:54 ` David Miller
2006-06-23 21:53 ` Benjamin LaHaise
2006-06-23 22:12 ` David Miller
2006-06-23 7:09 ` [2/4] kevent: network notifications Evgeniy Polyakov
2006-06-23 7:09 ` [3/4] kevent: fs/aio notifications Evgeniy Polyakov
2006-06-23 7:09 ` [4/4] kevent: generic poll and timer notifications Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 9:18 [0/4] kevent: generic event processing subsystem Evgeniy Polyakov
2006-07-26 9:18 ` [1/4] kevent: core files Evgeniy Polyakov
2006-07-26 10:31 ` Andrew Morton
2006-07-26 10:37 ` Evgeniy Polyakov
2006-07-26 10:44 ` 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=20060623213144.GF14126@kvack.org \
--to=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.