From: Jonathan Lahr <lahr@us.ibm.com>
To: Jens Axboe <axboe@suse.de>
Cc: lahr@beaverton.ibm.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: io_request_lock/queue_lock patch
Date: Fri, 31 Aug 2001 07:52:01 -0700 [thread overview]
Message-ID: <20010831075201.N23680@us.ibm.com> (raw)
In-Reply-To: <20010830134930.F23680@us.ibm.com> <20010831075613.A2855@suse.de>
In-Reply-To: <20010831075613.A2855@suse.de>; from axboe@suse.de on Fri, Aug 31, 2001 at 07:56:13AM +0200
Jens,
Please elaborate on "no, no, no". Are you suggesting that no further
improvements can be made or should be attempted on the 2.4 i/o subsystem?
Jonathan
Jens Axboe [axboe@suse.de] wrote:
> On Thu, Aug 30 2001, Jonathan Lahr wrote:
> >
> > Included below is a snapshot of a patch I am developing to reduce
> > io_request_lock contention in 2.4.
>
> No no no, you are opening a serious can of worms. No offense, but did
> you really think this would fly?! This is already being taken care of
> for 2.5, lets leave 2.4 alone in this regard.
>
> --
> Jens Axboe
--
Jonathan Lahr
IBM Linux Technology Center
Beaverton, Oregon
lahr@us.ibm.com
503-578-3385
next prev parent reply other threads:[~2001-08-31 14:56 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 [this message]
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=20010831075201.N23680@us.ibm.com \
--to=lahr@us.ibm.com \
--cc=axboe@suse.de \
--cc=lahr@beaverton.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 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.