From: Jens Axboe <axboe@suse.de>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
James Bottomley <James.Bottomley@steeleye.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
SCSI development list <linux-scsi@vger.kernel.org>,
USB Storage List <usb-storage@one-eyed-alien.net>
Subject: Re: Sysfs attribute file for max_sectors
Date: Tue, 6 Jan 2004 22:14:24 +0100 [thread overview]
Message-ID: <20040106211424.GS3483@suse.de> (raw)
In-Reply-To: <20040106131105.A12358@beaverton.ibm.com>
On Tue, Jan 06 2004, Patrick Mansfield wrote:
> Alan -
>
> Given that we currently don't have any user level intitiated scanning, how
> can you modify max_sectors in user space prior to the scsi_alloc_queue()
> call done during scan?
>
> Is there a block interface to modify max_sectors?
No. As James very clearly stated (and that I back 100%), max_sectors is
a driver template setting. It doesn't make sense to expose it, it's not
a configurable item.
--
Jens Axboe
next prev parent reply other threads:[~2004-01-06 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031207051634.GB21951@one-eyed-alien.net>
2003-12-08 16:15 ` Notify about errors during initialization Alan Stern
2004-01-05 2:10 ` Matthew Dharm
2004-01-05 22:04 ` Alan Stern
2004-01-05 22:13 ` Christoph Hellwig
2004-01-05 23:32 ` Mike Anderson
2004-01-06 16:17 ` Christoph Hellwig
2004-01-06 17:15 ` Patrick Mansfield
2004-01-06 17:18 ` Christoph Hellwig
2004-01-06 18:08 ` Mike Anderson
2004-01-06 18:08 ` Christoph Hellwig
2004-01-06 19:04 ` Mike Anderson
2004-01-06 18:07 ` Sysfs attribute file for max_sectors Alan Stern
2004-01-06 18:23 ` James Bottomley
2004-01-06 19:31 ` Alan Stern
2004-01-06 19:47 ` James Bottomley
2004-01-07 16:16 ` PATCH: (as168) " Alan Stern
2004-01-06 21:11 ` Patrick Mansfield
2004-01-06 21:14 ` Jens Axboe [this message]
2004-01-06 22:00 ` Alan Stern
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=20040106211424.GS3483@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@one-eyed-alien.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.