Re-Sending: Christoph, Here are the clarification for the design to implement the fast_load, cmd_per_lun and max_sectors: The fast_load parameter is for the user to decide at driver load time if (s)he wants to skip scan of devices in PD channels. After driver is loaded the user cannot be permitted to modify this value. If the user needs to see the devices in the PD channels, (s)he may initiate a scan via sysfs/proc based on the kernel being used. Once the user has done the scan, the fast_load value does not have any significance and thus not exposed for reading. cmd_per_lun & max_sectors are also intended to be provided by user only at driver load time. In the current implementation both these do appear as read-only values under host# in sysfs. The current design is not to allow these values to be modified on the fly. Regards, Bo Yang -----Original Message----- From: Yang, Bo Sent: Wednesday, October 31, 2007 10:14 AM To: Christoph Hellwig Cc: linux-scsi@xxxxxxxxxxxxxxx; James.Bottomley@xxxxxxxxxxxx; akpm@xxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Patro, Sumant; Kolli, Neela Subject: RE: [PATCH 3/8] scsi: megaraid_sas - add module param max_sectors, cmd_per_lun Christoph, Here are the clarification for the design to implement the fast_load, cmd_per_lun and max_sectors: The fast_load parameter is for the user to decide at driver load time if (s)he wants to skip scan of devices in PD channels. After driver is loaded the user cannot be permitted to modify this value. If the user needs to see the devices in the PD channels, (s)he may initiate a scan via sysfs/proc based on the kernel being used. Once the user has done the scan, the fast_load value does not have any significance and thus not exposed for reading. cmd_per_lun & max_sectors are also intended to be provided by user only at driver load time. In the current implementation both these do appear as read-only values under host# in sysfs. The current design is not to allow these values to be modified on the fly. Regards, Bo Yang -----Original Message----- From: Christoph Hellwig [mailto:hch@xxxxxxxxxxxxx] Sent: Tuesday, October 30, 2007 1:39 PM To: Yang, Bo Cc: linux-scsi@xxxxxxxxxxxxxxx; James.Bottomley@xxxxxxxxxxxx; akpm@xxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Patro, Sumant Subject: Re: [PATCH 3/8] scsi: megaraid_sas - add module param max_sectors, cmd_per_lun On Mon, Oct 01, 2007 at 11:51:48AM -0400, bo yang wrote: > +/* > + * Number of sectors per IO command will be set in megasas_init_mfi > + * if user does not provide > + */ > +static unsigned int max_sectors; > +module_param_named(max_sectors, max_sectors, int, 0); > +MODULE_PARM_DESC(max_sectors, > + "Maximum number of sectors per IO command"); > + > +/* > + * Number of cmds per logical unit > + */ > +static unsigned int cmd_per_lun = MEGASAS_DEFAULT_CMD_PER_LUN; > +module_param_named(cmd_per_lun, cmd_per_lun, int, 0); > +MODULE_PARM_DESC(cmd_per_lun, > + "Maximum number of commands per logical unit (default=128)"); I don't think this should be in drivers. cmd_per_lun is a scsi_host attribute already and you should change the mid-layer to add an optional host template method that allows the sysfs file to be writeable. max_sectors should be handled similar although we don't seem to have an attribute for it yet (maybe the block layer does?) - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
