public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pavel Pisa <pisa@cmp.felk.cvut.cz>
Subject: Re: [patch 1/2] epoll fix own poll()
Date: Thu, 29 Jan 2009 10:27:26 -0800	[thread overview]
Message-ID: <20090129102726.5f4a0040.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0901290956530.15448@alien.or.mcafeemobile.com>

On Thu, 29 Jan 2009 10:16:31 -0800 (PST) Davide Libenzi <davidel@xmailserver.org> wrote:

> On Thu, 29 Jan 2009, Andrew Morton wrote:
> 
> > >  fs/eventpoll.c |  510 +++++++++++++++++++++++++++++++++------------------------
> > >  1 file changed, 304 insertions(+), 206 deletions(-)
> > 
> > Holy cow man, this patch is HUGE!  I don't have a clue what it does nor
> > how it does it.  I'd be somewhat scared to merge it into 2.6.29.  How
> > serious is this bug?
> 
> It is a 3 in a scale of 5. The reason the patch is HUGE is because the 
> epoll ->poll() code now has to perform an operation similar to what was 
> performing in epoll_wait(), and under the same constraints (check out for 
> recursions and too long nesting chains) that were checked in the wakeups.
> So instead of duplicating the code, I made the two core operations such 
> that they get a function pointer for the core operation they have to 
> perform. That required some code movement.
> 

But which kernel version are you looking to get this merged into?

> 
> You always confuse me with your comments. Before you comment, then you 
> merge w/out giving me time to change.
>

yeah, I often do that.  If I see nothing fatal in the patch I'll merge
it so that it gets a bit of testing and so that it doesn't get
forgotten about.  Especially if it's a bugfix.

Sometimes I'll send a reply and the originator goes to sleep for weeks,
and stuff could even get lost.  I hate losing stuff.  I'll mark the patch
as "needs an update" in the series file so I don't accidentally merge it
upstream.

> Would you like the updated patches?

Sure, when convenient.

  reply	other threads:[~2009-01-29 18:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 20:54 [patch 1/2] epoll fix own poll() Davide Libenzi
2009-01-27 20:59 ` Davide Libenzi
2009-01-29  8:01 ` Andrew Morton
2009-01-29 18:16   ` Davide Libenzi
2009-01-29 18:27     ` Andrew Morton [this message]
2009-01-29 18:32       ` Davide Libenzi
2009-01-29 18:37         ` Andrew Morton
2009-01-29 18:43           ` Davide Libenzi
2009-01-30  2:29           ` Pavel Pisa
2009-01-30  2:52             ` Davide Libenzi
2009-01-30  7:41             ` Davide Libenzi
2009-01-30  9:42               ` Pavel Pisa
2009-01-30 18:40                 ` Davide Libenzi

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=20090129102726.5f4a0040.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pisa@cmp.felk.cvut.cz \
    /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