LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: David Miller <davem@davemloft.net>,
	Ulrich Drepper <drepper@redhat.com>,
	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>, Ingo Molnar <mingo@elte.hu>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [take35 0/10] kevent: Generic event handling mechanism.
Date: Mon, 12 Feb 2007 13:35:10 +0300	[thread overview]
Message-ID: <20070212103510.GC5703@2ka.mipt.ru> (raw)
In-Reply-To: <20070205142336.GA24190@2ka.mipt.ru>

On Mon, Feb 05, 2007 at 05:23:36PM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> On Thu, Feb 01, 2007 at 01:12:30PM +0300, Evgeniy Polyakov (johnpol@2ka.mipt.ru) wrote:
> > 
> > Generic event handling mechanism.
> > 
> > Kevent is a generic subsytem which allows to handle event notifications.
> > It supports both level and edge triggered events. It is similar to
> > poll/epoll in some cases, but it is more scalable, it is faster and
> > allows to work with essentially eny kind of events.
> > 
> > Events are provided into kernel through control syscall and can be read
> > back through ring buffer or using usual syscalls.
> > Kevent update (i.e. readiness switching) happens directly from internals
> > of the appropriate state machine of the underlying subsytem (like
> > network, filesystem, timer or any other).
> > 
> > Homepage:
> > http://tservice.net.ru/~s0mbre/old/?section=projects&item=kevent
> > 
> > Documentation page:
> > http://linux-net.osdl.org/index.php/Kevent
> > 
> > Consider for inclusion.
> > 
> > P.S. If you want to be removed from Cc: list just drop me a mail.
> > 
> > Changes from 'take34' patchset:
> >  * Ported to the 2.6.20-rc7 (9be5b038b1c9d1927c367bf91683458e10d5d4eb) tree.
> 
> Is there some progress?
> Some things to be implemented, described or discussed?

I think that mean that everybody is happy with APi, design and set of
features. 

Andrew, do you consider kevent for inclusion or declining?

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-02-12 10:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <asdasdqaa0591036@2ka.mipt.ru>
2007-02-01 10:12 ` Evgeniy Polyakov
2007-02-01 10:12   ` [take35 1/10] kevent: Description Evgeniy Polyakov
2007-02-01 10:12     ` [take35 2/10] kevent: Core files Evgeniy Polyakov
2007-02-01 10:12       ` [take35 3/10] kevent: poll/select() notifications Evgeniy Polyakov
2007-02-01 10:12         ` [take35 4/10] kevent: Socket notifications Evgeniy Polyakov
2007-02-01 10:12           ` [take35 5/10] kevent: Timer notifications Evgeniy Polyakov
2007-02-01 10:12             ` [take35 6/10] kevent: Pipe notifications Evgeniy Polyakov
2007-02-01 10:12               ` [take35 7/10] kevent: Signal notifications Evgeniy Polyakov
2007-02-01 10:12                 ` [take35 8/10] kevent: Kevent posix timer notifications Evgeniy Polyakov
2007-02-01 10:12                   ` [take35 9/10] kevent: Private userspace notifications Evgeniy Polyakov
2007-02-01 10:12                     ` [take35 10/10] kevent: Kevent based AIO (aio_sendfile()/aio_sendfile_path()) Evgeniy Polyakov
2007-02-02 11:58                       ` /async open+send/ " Evgeniy Polyakov
2007-02-05 14:23   ` [take35 0/10] kevent: Generic event handling mechanism Evgeniy Polyakov
2007-02-12 10:35     ` Evgeniy Polyakov [this message]
2007-02-12 14:59       ` Ulrich Drepper
2007-02-13  5:08         ` Evgeniy Polyakov
2007-02-12 17:13       ` Andrew Morton
2007-02-13  5:14         ` Evgeniy Polyakov
2007-02-05 17:28   ` David M. Lloyd
2007-02-05 17:45     ` 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=20070212103510.GC5703@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --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=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=zach.brown@oracle.com \
    --subject='Re: [take35 0/10] kevent: Generic event handling mechanism.' \
    /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

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).