From: Andrew Morton <akpm@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2] fix epoll single pass code and add wait-exclusive flag ...
Date: Sun, 13 May 2007 12:29:50 -0700 [thread overview]
Message-ID: <20070513122950.e30f2c80.akpm@linux-foundation.org> (raw)
In-Reply-To: <send-serie.davidel@xmailserver.org.27693.1178937031.1>
On Fri, 11 May 2007 19:30:31 -0700 Davide Libenzi <davidel@xmailserver.org> wrote:
> Fixes the epoll single pass code. During the unlocked event delivery
> (to userspace) code, the poll callback can re-issue new events, and
> we must receive them correctly. Since we loop in a lockless fashion,
> we want to be O(nready), and we don't want to flash on/off the spinlock
> for every event, we have the poll callback to use a secondary list to
> queue events while we're inside the event delivery loop.
> The rw_semaphore has been turned into a mutex.
> This patch also adds the wait-exclusive flag, as suggested by Davi Arnaut.
>
> ...
> @@ -534,6 +547,8 @@
> }
>
> mutex_unlock(&epmutex);
> +
> + mutex_destroy(&ep->mtx);
> }
It's a little alarming to see a dereference of `ep' right at the end of a
function called ep_free(ep).
Code is OK, but perhaps the kfree(ep) should be moved into ep_free()?
I'm a bit stunned at the size of these two patches.
next prev parent reply other threads:[~2007-05-13 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 2:30 [patch 1/2] fix epoll single pass code and add wait-exclusive flag Davide Libenzi
2007-05-13 19:29 ` Andrew Morton [this message]
2007-05-13 19:37 ` 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=20070513122950.e30f2c80.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@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.