From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Warning: about not setting max_sectors
Date: Tue, 10 Dec 2002 13:23:48 +0000 [thread overview]
Message-ID: <20021210132348.A31628@infradead.org> (raw)
In-Reply-To: <200212091455.gB9Etg601956@localhost.localdomain>; from James.Bottomley@steeleye.com on Mon, Dec 09, 2002 at 08:55:41AM -0600
On Mon, Dec 09, 2002 at 08:55:41AM -0600, James Bottomley wrote:
> For some reason, the SCSI core is now warning about drivers which don't set
> max_sectors.
>
> Just for the record, we have two parameters in the template:
>
> sg_tablesize which determines the maximum number of scatter gather entries the
> host can have (corresponds to max_phys_segments in the block layer), and
>
> max_sectors, which imposes a maximum overall transfer length (corresponds to
> max_sectors in the block queue).
>
> The comments over max_sectors list it as optional (if unset, we set it to the
> scsi equivalent of machine infinity---well, actually 1024, or 512Mb for usual
> blocks).
>
> The reason it's unset on so many drivers is that usually, they have no
> absolute transfer limit, so they're just bounded by the number of entries in
> the scatter-gather list.
>
> I can't see a reason to force every driver suddenly to have an arbitrary
> max_sectors, so if no-one objects, I'll pull out the warning.
I added this intentionally. The default is set in scsi_register_host
which is an obsolete interface. This warning reminds driver writers to set
the value explicitly, with scsi_add_host & friends they won't get a default
anymore.
next prev parent reply other threads:[~2002-12-10 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 14:55 Warning: about not setting max_sectors James Bottomley
2002-12-10 13:23 ` Christoph Hellwig [this message]
2002-12-10 14:13 ` GOTO Masanori
2002-12-10 14:47 ` James Bottomley
2002-12-11 10:57 ` Christoph Hellwig
2002-12-11 14:37 ` James Bottomley
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=20021210132348.A31628@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--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