From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Robert Iakobashvili <coroberti@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [1/1] Kevent subsystem.
Date: Fri, 23 Jun 2006 09:50:23 +0400 [thread overview]
Message-ID: <20060623055019.GA7771@2ka.mipt.ru> (raw)
In-Reply-To: <7e63f56c0606221253k7e3d28eejc75bf1be4304c389@mail.gmail.com>
On Thu, Jun 22, 2006 at 09:53:38PM +0200, Robert Iakobashvili (coroberti@gmail.com) wrote:
> Evgeniy,
>
> On 6/22/06, Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
>
> >Kevent subsystem incorporates several AIO/kqueue design notes and ideas.
> >Kevent can be used both for edge and level notifications. It supports
> >socket notifications, network AIO (aio_send(), aio_recv() and
> >aio_sendfile()), inode notifications (create/remove),
> >generic poll()/select() notifications and timer notifications.
>
> Great job!
> Smooth integration with userland asynch POSIX frameworks
> (e.g. ACE POSIX_Proactor) may require syscalls (or their emulation)
> with POSIX interface:
>
> * POSIX_API
> * aio_read
> * aio_write
> * aio_suspend
> * aio_error
> * aio_return
> * aio_cancel
>
> where aio_suspend is very important.
I've designed network AIO differently as how posix declared it's
functions. POSIX AIO is like rocket science - while one tries to
implement them all there is no time to do the real work.
Although all of them including suspend can be emulated on top of
existing calls to kevent.
> --
> Sincerely,
> ------------------------------------------------------------------
> Robert Iakobashvili, coroberti at gmail dot com
> Navigare necesse est, vivere non est necesse.
> ------------------------------------------------------------------
--
Evgeniy Polyakov
next prev parent reply other threads:[~2006-06-23 5:50 UTC|newest]
Thread overview: 28+ 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 [this message]
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
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-04-28 19:59 [PATCH 1/3] Rough VJ Channel Implementation - vj_core.patch Evgeniy Polyakov
2006-04-28 22:00 ` David S. Miller
[not found] ` <20060429124451.GA19810@2ka.mipt.ru>
2006-05-01 21:32 ` David S. Miller
2006-05-02 8:10 ` [1/1] Kevent subsystem 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=20060623055019.GA7771@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=coroberti@gmail.com \
--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 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).