From: Jonathan Lahr <lahr@us.ibm.com>
To: Eric Youngdale <eric@andante.org>
Cc: "Gérard Roudier" <groudier@free.fr>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: io_request_lock/queue_lock patch
Date: Thu, 30 Aug 2001 16:07:08 -0700 [thread overview]
Message-ID: <20010830160708.G23680@us.ibm.com> (raw)
In-Reply-To: <20010830232228.C2120-100000@gerard> <008801c1319d$57f16970$4d0310ac@fairfax.mkssoftware.com>
In-Reply-To: <008801c1319d$57f16970$4d0310ac@fairfax.mkssoftware.com>; from eric@andante.org on Thu, Aug 30, 2001 at 05:47:19PM -0400
Is there an estimate on when the 2.5 i/o subsystem will be released?
Jonathan
Eric Youngdale [eric@andante.org] wrote:
> I am afraid I would have to agree with Gérard. We were planning on
> cleaning this mess up in the 2.5 kernel, and my inclination would be to
> leave this alone until then.
>
> -Eric
>
> ----- Original Message -----
> From: "Gérard Roudier" <groudier@free.fr>
> To: "Jonathan Lahr" <lahr@us.ibm.com>
> Cc: <linux-kernel@vger.kernel.org>; <linux-scsi@vger.kernel.org>
> Sent: Thursday, August 30, 2001 5:32 PM
> Subject: Re: io_request_lock/queue_lock patch
>
>
> >
> > Here are my welcome comments. :)
> >
> > In my opinion, it would well be a miracle if your patch does not introduce
> > new race conditions, at least for drivers that still use the old scsi done
> > method.
> >
> > Gérard.
next prev parent reply other threads:[~2001-08-30 23:13 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 [this message]
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
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=20010830160708.G23680@us.ibm.com \
--to=lahr@us.ibm.com \
--cc=eric@andante.org \
--cc=groudier@free.fr \
--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