All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Youngdale" <eric@andante.org>
To: "Jonathan Lahr" <lahr@us.ibm.com>, "Jens Axboe" <axboe@suse.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>
Subject: Re: io_request_lock patch?
Date: Tue, 10 Jul 2001 16:09:19 -0400	[thread overview]
Message-ID: <00a401c1097c$343d45b0$4d0310ac@fairfax.mkssoftware.com> (raw)
In-Reply-To: <20010709123936.E6013@us.ibm.com> <20010709214453.U16505@suse.de> <20010710124903.H6013@us.ibm.com>


    The bit that I had automated was to essentially fix each and every
low-level SCSI driver such that each low-level driver would be responsible
for it's own locking.  At this point the patches and the tool are on hold -
once the 2.5 kernel series gets underway, I can generate some fairly massive
patchsets.

-Eric

----- Original Message -----
From: "Jonathan Lahr" <lahr@us.ibm.com>
To: "Jens Axboe" <axboe@suse.de>
Cc: <linux-kernel@vger.kernel.org>; <linux-scsi@vger.kernel.org>
Sent: Tuesday, July 10, 2001 3:49 PM
Subject: Re: io_request_lock patch?


> Jens Axboe [axboe@suse.de] wrote:
> > On Mon, Jul 09 2001, Jonathan Lahr wrote:
> > >
> > > I have heard that a patch to reduce io_request_lock contention by
> > > breaking it into per queue locks was released in the past.  Does
> > > anyone know where I could find this patch if it exists?
> >
> > I had a patch about a year ago that did it safely for the block layer
> > and IDE at least, and also for selected SCSI hba's. Some of the latter
> > variety are pretty hard and/or tedious to fixup, Eric Y has done some
> > work automating this process almost completely. Until that is done, the
> > general patch has no chance of being integrated.
>
> I am investigating reducing io_request_lock contention in the shorter term
> if possible with smaller incremental modifications.  So I'm first trying
to
> discover any previous work that might have been done toward this purpose.
>
> --
> Jonathan Lahr
> IBM Linux Technology Center
> Beaverton, Oregon
> lahr@us.ibm.com
> 503-578-3385
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
>


  reply	other threads:[~2001-07-10 20:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09 19:39 io_request_lock patch? Jonathan Lahr
2001-07-09 19:44 ` Jens Axboe
2001-07-10 19:49   ` Jonathan Lahr
2001-07-10 20:09     ` Eric Youngdale [this message]
2001-07-11  8:05       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2001-07-10 11:55 Dipankar Sarma
2001-07-10 23:05 ` Mike Anderson
2001-07-11  7:15   ` Jens Axboe
2001-07-11  8:53   ` Dipankar Sarma
2001-07-11  8:53     ` Jens Axboe
2001-07-11 14:02       ` Dipankar Sarma
2001-07-11 14:01         ` Jens Axboe
2001-07-11 14:55           ` Dipankar Sarma
2001-07-11 19:16             ` Jens Axboe
2001-07-11 16:02     ` Mike Anderson
2001-07-11 19:20       ` Jens Axboe
2001-07-11 20:13         ` Dipankar Sarma
2001-07-11 20:17           ` Jens Axboe
2001-07-11 21:05             ` Mike Anderson
2001-07-11  7:19 ` Jens Axboe
2001-07-11  8:39   ` Dipankar Sarma
2001-07-11  8:47     ` 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='00a401c1097c$343d45b0$4d0310ac@fairfax.mkssoftware.com' \
    --to=eric@andante.org \
    --cc=axboe@suse.de \
    --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.