From: Jonathan Lahr <lahr@us.ibm.com>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
lse-tech@lists.sourceforge.net
Subject: SCSI io_request_lock patch
Date: Mon, 12 Nov 2001 13:09:02 -0800 [thread overview]
Message-ID: <20011112130902.B26302@us.ibm.com> (raw)
This is a request for comments on the patch described below which
implements a revised approach to reducing io_request_lock contention
in 2.4.
This new version of the io_request_lock patch (siorl-v0) is available
at http://sourceforge.net/projects/lse/. It employs the same
concurrent request queueing scheme as the iorlv0 patch but isolates
code changes to the SCSI subsystem and engages the new locking scheme
only for SCSI drivers which explicitly request it. I took this more
restricted approach after additional development based on comments from
Jens and others indicated that iorlv0 impacted the IDE subsystem and
was unnecessarily broad in general.
The siorl-v0 patch allows drivers to enable concurrent queueing through
the concurrent_queue field in the Scsi_Host_Template which is copied to
the request queue. It creates SCSI-specific versions of generic block
i/o functions used by the SCSI subsystem and modifies them to conditionally
engage the new locking scheme based on this field. It allows control over
which drivers use concurrent queueing and preserves original block i/o
behavior by default.
I tested this patch with aic7xxx and lpfc drivers, and regression tested
it with IDE disk and CDROM drivers. Any feedback would be appreciated.
Thanks,
Jonathan
--
Jonathan Lahr
IBM Linux Technology Center
Beaverton, Oregon
lahr@us.ibm.com
503-578-3385
next reply other threads:[~2001-11-12 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 21:09 Jonathan Lahr [this message]
2001-11-13 8:23 ` [Lse-tech] SCSI io_request_lock patch Jens Axboe
2001-11-13 18:42 ` Jonathan Lahr
2001-11-14 8:11 ` Jens Axboe
2001-11-14 18:54 ` Jonathan Lahr
2001-11-15 10:23 ` Jens Axboe
2001-11-15 18:15 ` Jonathan Lahr
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=20011112130902.B26302@us.ibm.com \
--to=lahr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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