From: "David C. Hansen" <haveblue@us.ibm.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Moving BKL from generic code into drivers
Date: Tue, 04 Dec 2001 19:20:47 -0800 [thread overview]
Message-ID: <3C0D928F.8080904@us.ibm.com> (raw)
As a first step toward removing the BKL from some block device drivers,
I'm planning on moving the BKL out of the generic code and into the
drivers themselves.
I plan on doing this indiscriminately. All block devices will have a
lock_kernel() at the top of their open() and an unlock_kernel() at the
bottom. Later on, we can remove it from individual drivers as we see fit.
Now the big question:
In block_dev.c:do_open(), the BKL is held in addition to bdev->bd_sem.
Why is the BKL held here, other than to protect all of the drivers' open
functions? What doesn't the semaphore provide?
This kind of action, moving the BKL from generic code into drivers isn't
a first:
http://marc.theaimsgroup.com/?l=linux-kernel&m=96346538231916&w=2
--
Dave Hansen
haveblue@us.ibm.com
next reply other threads:[~2001-12-05 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 3:20 David C. Hansen [this message]
2001-12-05 4:03 ` Moving BKL from generic code into drivers Alexander Viro
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=3C0D928F.8080904@us.ibm.com \
--to=haveblue@us.ibm.com \
--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