From: Matthew Wilcox <matthew@wil.cx>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>,
Christoph Hellwig <hch@lst.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
"J. Bruce Fields" <bfields@fieldses.org>,
Andrew Morton <akpm@linux-foundation.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, John Kacur <jkacur@redhat.com>,
Sage Weil <sage@newdream.net>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/locks.c: prepare for BKL removal
Date: Sat, 18 Sep 2010 07:48:20 -0600 [thread overview]
Message-ID: <20100918134819.GB25139@parisc-linux.org> (raw)
In-Reply-To: <1284815371-5843-1-git-send-email-arnd@arndb.de>
On Sat, Sep 18, 2010 at 03:09:31PM +0200, Arnd Bergmann wrote:
> This prepares the removal of the big kernel lock from the
> file locking code. We still use the BKL as long as fs/lockd
> uses it and ceph might sleep, but we can flip the definition
> to a private spinlock as soon as that's done.
> All users outside of fs/lockd get converted to use
> lock_flocks() instead of lock_kernel() where appropriate.
>
> Based on an earlier patch to use a spinlock from Matthew
> Wilcox, who has attempted this a few times before. An even
> earlier attempt to use a semaphore instead of the BKL
> apparently was made by Andrew Morton about ten years ago,
> but reverted for performance reasons.
Actually, I attempted the semaphore conversion ten years ago, but Andrew
Morton reverted it due to the performance regression. I believe it was
Apache, when it was using file locks to synchronise between threads.
Patch looks good; Acked-by: Matthew Wilcox <willy@linux.intel.com>
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2010-09-18 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 13:09 [PATCH] fs/locks.c: prepare for BKL removal Arnd Bergmann
2010-09-18 13:48 ` Matthew Wilcox [this message]
2010-09-19 19:34 ` J. Bruce Fields
2010-09-20 3:59 ` Sage Weil
2010-09-20 6:07 ` Stephen Rothwell
2010-09-21 16:12 ` Sage Weil
2010-09-21 20:09 ` Arnd Bergmann
2010-09-23 3:42 ` Sage Weil
2010-09-23 6:40 ` Arnd Bergmann
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=20100918134819.GB25139@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bfields@fieldses.org \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=jkacur@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mszeredi@suse.cz \
--cc=sage@newdream.net \
--cc=trond.myklebust@fys.uio.no \
--cc=willy@linux.intel.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.