From: Mike Christie <michaelc@cs.wisc.edu>
To: axboe@suse.de, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/10] remove scsi_request usage from sg and st
Date: Tue, 08 Nov 2005 10:54:58 -0600 [thread overview]
Message-ID: <4370D862.6080602@cs.wisc.edu> (raw)
In-Reply-To: <1131444389.23111.56.camel@max>
Mike Christie wrote:
> We will probably hit many problems with LLDs using low max_hw_sectors,
> because they have not been converted to export their real values on the
> host template so I think these patches should sit in scsi-misc for a
> good deal of time.
>
oh yeah just to clarify, this patch [PATCH 2/10] seperate max sectors
and max hw sectors, makes it so the scsi host template's max_sectors is
passed up as q->max_hw_sectors. I did not know the correct limit for any
SCSI LLD's sht->max_sectors so I could not convert them if they were
previously setting a conservtaive value for reasons like libata.
next prev parent reply other threads:[~2005-11-08 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 10:06 [PATCH 0/10] remove scsi_request usage from sg and st Mike Christie
2005-11-08 10:10 ` Mike Christie
2005-11-08 16:54 ` Mike Christie [this message]
2005-11-10 10:55 ` Christoph Hellwig
2005-11-10 12:51 ` Mike Christie
2005-11-10 13:02 ` Christoph Hellwig
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=4370D862.6080602@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=axboe@suse.de \
--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 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).