From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: Sysfs attribute file for max_sectors Date: Tue, 6 Jan 2004 22:14:24 +0100 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <20040106211424.GS3483@suse.de> References: <1073413440.2221.47.camel@mulgrave> <20040106131105.A12358@beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from ns.virtualhost.dk ([195.184.98.160]:16517 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S265115AbUAFVOn (ORCPT ); Tue, 6 Jan 2004 16:14:43 -0500 Content-Disposition: inline In-Reply-To: <20040106131105.A12358@beaverton.ibm.com> List-Id: linux-scsi@vger.kernel.org To: Patrick Mansfield Cc: Alan Stern , James Bottomley , Christoph Hellwig , Matthew Dharm , SCSI development list , USB Storage List 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