From: Jan Harkes <jaharkes@cs.cmu.edu>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: [RFC][PATCH 0/3] Coda: remove BKL
Date: Wed, 20 Oct 2010 16:23:01 -0400 [thread overview]
Message-ID: <1287606184-26889-1-git-send-email-jaharkes@cs.cmu.edu> (raw)
The following three patches remove the big kernel lock from the Coda
file system kernel module. We initially add a spinlock to protect the
Coda-specific inode data. After this we can push the BKL all the way
down to where the requests are queued for the userspace Coda cache
manager process and finally we replace the remaining BKL uses with a
mutex that protects the upcall queues.
Yoshihisa Abe (3):
Coda: add spin lock to protect accesses to struct coda_inode_info.
Coda: push BKL regions into coda_upcall()
Coda: replace BKL with mutex
fs/coda/cache.c | 17 ++++--
fs/coda/cnode.c | 19 ++++--
fs/coda/dir.c | 158 ++++++++++++++------------------------------
fs/coda/file.c | 31 ++++-----
fs/coda/inode.c | 57 +++++++++-------
fs/coda/pioctl.c | 22 ++-----
fs/coda/psdev.c | 30 +++++----
fs/coda/symlink.c | 3 -
fs/coda/upcall.c | 24 +++++--
include/linux/coda_fs_i.h | 13 +++-
include/linux/coda_linux.h | 6 ++-
include/linux/coda_psdev.h | 2 +
12 files changed, 177 insertions(+), 205 deletions(-)
next reply other threads:[~2010-10-20 20:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 20:23 Jan Harkes [this message]
2010-10-20 20:23 ` [RFC][PATCH 1/3] Coda: add spin lock to protect accesses to struct coda_inode_info Jan Harkes
2010-10-20 20:23 ` [RFC][PATCH 2/3] Coda: push BKL regions into coda_upcall() Jan Harkes
2010-10-20 20:23 ` [RFC][PATCH 3/3] Coda: replace BKL with mutex Jan Harkes
2010-10-21 9:08 ` [RFC][PATCH 0/3] Coda: remove BKL Arnd Bergmann
2010-10-21 15:14 ` Jan Harkes
2010-10-21 15:20 ` 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=1287606184-26889-1-git-send-email-jaharkes@cs.cmu.edu \
--to=jaharkes@cs.cmu.edu \
--cc=arnd@arndb.de \
--cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).