From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Hellwig <hch@lst.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
mpm@selenic.com, dada1@cosmosbay.com,
linux-kernel@vger.kernel.org, andi@firstfloor.org,
oleg@redhat.com, viro@zeniv.linux.org.uk,
davidel@xmailserver.org, davem@davemloft.net,
linux-api@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 2/4] Convert epoll to a bitlock
Date: Wed, 4 Feb 2009 18:20:18 +1100 [thread overview]
Message-ID: <200902041820.20535.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20090204071320.GA19348@lst.de>
On Wednesday 04 February 2009 18:13:20 Christoph Hellwig wrote:
> On Tue, Feb 03, 2009 at 04:19:31PM -0700, Jonathan Corbet wrote:
> > 1) Use i_lock to protect accesses to f_flags. This would enable some
> > BKL usage to be removed, but would not fix fasync.
>
> What about just turning f_ep_lock into f_lock and using it?
Ah, yes I was going to say that too, but I confused i_lock with i_mutex
because it sounded like Jon needed a sleeping lock here?
Agree f_lock would be good. It might come in handy for other things too.
next prev parent reply other threads:[~2009-02-04 7:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 18:20 [PATCH/RFC] F_SETFL/Fasync BKL removal, now without unsightly global locks Jonathan Corbet
2009-02-02 18:20 ` [PATCH 1/4] Use bit operations for file->f_flags Jonathan Corbet
2009-02-03 21:37 ` Andrew Morton
2009-02-02 18:20 ` [PATCH 2/4] Convert epoll to a bitlock Jonathan Corbet
2009-02-03 21:39 ` Andrew Morton
2009-02-03 21:55 ` Eric Dumazet
2009-02-03 22:05 ` Andrew Morton
2009-02-03 22:22 ` Matt Mackall
2009-02-03 22:37 ` Jonathan Corbet
2009-02-03 22:53 ` Andrew Morton
2009-02-03 23:09 ` Davide Libenzi
2009-02-03 23:12 ` Davide Libenzi
2009-02-03 23:19 ` Jonathan Corbet
2009-02-03 23:29 ` Andrew Morton
2009-02-04 7:13 ` Christoph Hellwig
2009-02-04 7:20 ` Nick Piggin [this message]
2009-02-04 13:34 ` Jonathan Corbet
2009-02-04 16:51 ` Davide Libenzi
2009-02-03 23:08 ` Davide Libenzi
2009-02-04 2:48 ` Eric Dumazet
2009-02-04 1:00 ` wli
2009-02-04 4:54 ` Nick Piggin
2009-02-02 18:20 ` [PATCH 3/4] Move FASYNC bit handling to f_op->fasync() Jonathan Corbet
2009-02-02 18:20 ` [PATCH 4/4] Rationalize fasync return values Jonathan Corbet
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=200902041820.20535.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=corbet@lwn.net \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=davidel@xmailserver.org \
--cc=hch@lst.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=oleg@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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