All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jonathan Lahr <lahr@us.ibm.com>
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 20:03:33 +0200	[thread overview]
Message-ID: <20010831200333.A9069@suse.de> (raw)
In-Reply-To: <20010830134930.F23680@us.ibm.com> <20010831075613.A2855@suse.de> <20010831075201.N23680@us.ibm.com>
In-Reply-To: <20010831075201.N23680@us.ibm.com>; from lahr@us.ibm.com on Fri, Aug 31, 2001 at 07:52:01AM -0700

On Fri, Aug 31 2001, Jonathan Lahr wrote:
> 
> 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?

Of course not. The no no no just means that attempting to globally remove the
io_request_lock at this point is a no-go, so don't even go there. The
sledgehammer approach will not fly at this point, it's just way too risky.

Jens

  reply	other threads:[~2001-08-31 18: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 [this message]
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=20010831200333.A9069@suse.de \
    --to=axboe@suse.de \
    --cc=lahr@beaverton.ibm.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 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.