From: Jens Axboe <axboe@suse.de>
To: Peter Rival <frival@zk3.dec.com>
Cc: Jonathan Lahr <lahr@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: io_request_lock/queue_lock patch
Date: Thu, 6 Sep 2001 08:03:29 +0200 [thread overview]
Message-ID: <20010906080329.F576@suse.de> (raw)
In-Reply-To: <20010830134930.F23680@us.ibm.com> <20010831075613.A2855@suse.de> <20010831075201.N23680@us.ibm.com> <20010831200333.A9069@suse.de> <20010831113308.A28193@us.ibm.com> <20010903090703.C6875@suse.de> <3B968B82.80405@zk3.dec.com>
In-Reply-To: <3B968B82.80405@zk3.dec.com>
On Wed, Sep 05 2001, Peter Rival wrote:
> Jens Axboe wrote:
> >You are now browsing the request list without agreeing on what lock is
> >being held -- what happens to drivers assuming that io_request_lock
> >protects the list? Boom. For 2.4 we simply cannot afford to muck around
> >with this, it's jsut too dangerous. For 2.5 I already completely removed
> >the io_request_lock (also helps to catch references to it from drivers).
>
> Is this part of the bio patches? (I confess, I haven't had the time to
> look yet.) If not, do you know when we'll be seeing sneak previews of
> this code? (Yes, it's me again! ;)
Yep it's part of the bio patch. bio-14 for 2.4.10-preX is pending today
or tomorrow.
--
Jens Axboe
prev parent reply other threads:[~2001-09-06 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-30 20:49 io_request_lock/queue_lock patch Jonathan Lahr
2001-08-30 21:32 ` Gérard Roudier
2001-08-30 21:47 ` Eric Youngdale
2001-08-30 23:07 ` Jonathan Lahr
2001-08-31 5:57 ` Jens Axboe
2001-08-31 5:56 ` Jens Axboe
2001-08-31 14:52 ` Jonathan Lahr
2001-08-31 18:03 ` Jens Axboe
2001-08-31 18:33 ` Jonathan Lahr
2001-09-03 7:07 ` Jens Axboe
2001-09-04 16:46 ` Jonathan Lahr
2001-09-04 17:17 ` Jens Axboe
2001-09-05 20:30 ` Peter Rival
2001-09-06 6:03 ` Jens Axboe [this message]
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=20010906080329.F576@suse.de \
--to=axboe@suse.de \
--cc=frival@zk3.dec.com \
--cc=lahr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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