All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Jeff Garzik <jeff@garzik.org>
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, Jamal Hadi Salim <hadi@cyberus.ca>,
	Ingo Molnar <mingo@elte.hu>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [take32 0/10] kevent: Generic event handling mechanism.
Date: Wed, 10 Jan 2007 15:14:09 +0300	[thread overview]
Message-ID: <20070110121409.GA28862@2ka.mipt.ru> (raw)
In-Reply-To: <45A4D478.2030200@garzik.org>

On Wed, Jan 10, 2007 at 06:56:40AM -0500, Jeff Garzik (jeff@garzik.org) wrote:
> >It was there, but Andrew dropped it somewhere about take25 :)
> 
> Probably because it was a moving target with a high rate of change, 
> requiring time that Andrew did not have just to keep in sync and fix 
> build conflicts with other -mm patches.

Ok, I understood.
Let's freeze kevent for a while and allow things to settle down, but...

How can I detect that it is in use, since I get no feedback?
I suppose that if Andrew will not pick it up, I will resend/push/pull 
the latest set, but without new features implemented (or as addon), only
bugfixes.

> 	Jeff
> 

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-01-10 12:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <315adqaa0591036@2ka.mipt.ru>
2007-01-10  8:16 ` [take32 0/10] kevent: Generic event handling mechanism Evgeniy Polyakov
2007-01-10  8:16   ` [take32 1/10] kevent: Description Evgeniy Polyakov
2007-01-10  8:16     ` [take32 2/10] kevent: Core files Evgeniy Polyakov
2007-01-10  8:16       ` [take32 3/10] kevent: poll/select() notifications Evgeniy Polyakov
2007-01-10  8:16         ` [take32 4/10] kevent: Socket notifications Evgeniy Polyakov
2007-01-10  8:16           ` [take32 5/10] kevent: Timer notifications Evgeniy Polyakov
2007-01-10  8:16             ` [take32 6/10] kevent: Pipe notifications Evgeniy Polyakov
2007-01-10  8:16               ` [take32 7/10] kevent: Signal notifications Evgeniy Polyakov
2007-01-10  8:16                 ` [take32 8/10] kevent: Kevent posix timer notifications Evgeniy Polyakov
2007-01-10  8:16                   ` [take32 9/10] kevent: Private userspace notifications Evgeniy Polyakov
2007-01-10  8:16                     ` [take32 10/10] kevent: Kevent based AIO (aio_sendfile()) Evgeniy Polyakov
2007-01-10 11:11   ` [take32 0/10] kevent: Generic event handling mechanism Jeff Garzik
2007-01-10 11:30     ` Evgeniy Polyakov
2007-01-10 11:56       ` Jeff Garzik
2007-01-10 12:14         ` Evgeniy Polyakov [this message]
2007-01-10 12:18       ` Kevent bonus: epoll implementaion over kevent 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=20070110121409.GA28862@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 \
    /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.