From: Jens Axboe <axboe@suse.de>
To: "Mukker, Atul" <atulm@lsil.com>
Cc: "Bagalkote, Sreenivas" <sreenib@lsil.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
"'linux-megaraid-devel@dell.com'" <linux-megaraid-devel@dell.com>
Subject: Re: [ANNOUNCE] megaraid 2.00.6 patch for kernels without hostlock
Date: Fri, 1 Aug 2003 07:49:23 +0200 [thread overview]
Message-ID: <20030801054923.GM22104@suse.de> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570185F3CF@EXA-ATLANTA.se.lsil.com>
On Thu, Jul 31 2003, Mukker, Atul wrote:
>
> Well, that's definitely a good idea. Expect a new driver with this change.
> BTW, is there a kernel version beyond which all versions would support per
> host lock, and I mean a 2.4.x kernel :-)
Unfortunately no, however it is trivial to just add host->lock pointer
and make it point to io_request_lock. Ditto for q->queue_lock. That wont
change how the code operates at all. I will probably do that once 2.4.23
opens, it would make maintaining 2.6/2.4 drivers much easier (and ditto
for vendor kernels).
--
Jens Axboe
next prev parent reply other threads:[~2003-08-01 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 21:10 [ANNOUNCE] megaraid 2.00.6 patch for kernels without hostlock Mukker, Atul
2003-07-31 23:14 ` Matthew Wilcox
2003-08-01 5:49 ` Jens Axboe [this message]
2003-08-01 13:54 ` Disk speed differences under 2.6.0 Gordon Larsen
2003-08-01 14:55 ` Måns Rullgård
2003-08-04 14:12 ` Gordon Larsen
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 21:00 [ANNOUNCE] megaraid 2.00.6 patch for kernels without hostlock Bagalkote, Sreenivas
2003-07-31 9:05 ` 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=20030801054923.GM22104@suse.de \
--to=axboe@suse.de \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-megaraid-devel@dell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sreenib@lsil.com \
/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;
as well as URLs for NNTP newsgroup(s).