From: "Mukker, Atul" <atulm@lsil.com>
To: "'Jens Axboe'" <axboe@suse.de>,
"Bagalkote, Sreenivas" <sreenib@lsil.com>
Cc: "'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: Thu, 31 Jul 2003 17:10:50 -0400 [thread overview]
Message-ID: <0E3FA95632D6D047BA649F95DAB60E570185F3CF@EXA-ATLANTA.se.lsil.com> (raw)
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 :-)
Thanks
-Atul Mukker
> -----Original Message-----
> From: Jens Axboe [mailto:axboe@suse.de]
> Sent: Thursday, July 31, 2003 5:06 AM
> To: Bagalkote, Sreenivas
> Cc: 'linux-kernel@vger.kernel.org'; 'linux-scsi@vger.kernel.org';
> 'linux-megaraid-devel@dell.com'
> Subject: Re: [ANNOUNCE] megaraid 2.00.6 patch for kernels without
> hostlock
>
>
> On Wed, Jul 30 2003, Bagalkote, Sreenivas wrote:
> > Please apply this patch to megaraid 2.00.6 driver for
> kernels that don't
> > support per host lock. This can be found at :
> >
> > ftp://ftp.lsil.com/pub/linux-megaraid/drivers/version-2.00.6/
>
> It's easily possible to keep the impact of maintaining a driver across
> such kernels a lot smaller, by simply using the same lock in the
> spin_lock calls and just assign that lock to adapter->lock or
> io_request_lock depending on the kernel.
>
> --
> Jens Axboe
>
> _______________________________________________
> Linux-megaraid-devel mailing list
> Linux-megaraid-devel@dell.com
> http://lists.us.dell.com/mailman/listinfo/linux-megaraid-devel
> Please read the FAQ at http://lists.us.dell.com/faq or search
> the list archives at http://lists.us.dell.com/htdig/
>
next reply other threads:[~2003-07-31 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 21:10 Mukker, Atul [this message]
2003-07-31 23:14 ` [ANNOUNCE] megaraid 2.00.6 patch for kernels without hostlock Matthew Wilcox
2003-08-01 5:49 ` Jens Axboe
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=0E3FA95632D6D047BA649F95DAB60E570185F3CF@EXA-ATLANTA.se.lsil.com \
--to=atulm@lsil.com \
--cc=axboe@suse.de \
--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).