From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Yang, Bo" <Bo.Yang@lsi.com>
Cc: linux-scsi@vger.kernel.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, "Patro,
Sumant" <Sumant.Patro@lsi.com>,
"Kolli, Neela" <Neela.Kolli@lsi.com>
Subject: RE: [PATCH 1/8] scsi: megaraid_sas - add hibernation support
Date: Wed, 31 Oct 2007 12:12:24 -0500 [thread overview]
Message-ID: <1193850744.3411.69.camel@localhost.localdomain> (raw)
In-Reply-To: <9738BCBE884FDB42801FAD8A7769C265010A0A11@NAMAIL1.ad.lsil.com>
On Wed, 2007-10-31 at 07:25 -0600, Yang, Bo wrote:
> James,
> I did respond to Randy earlier.
Sorry, I couldn't find it in the archive when I looked ... although the
scsi reflector seems to be missing quite a few of your emails for some
reason.
> About the module params being added :
>
> 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.
fastload sounds reasonable. cmd_per_lun and max_sectors could
reasonably be altered at runtime ... just execute and unbind and rebind
operation to make them take effect.
James
next prev parent reply other threads:[~2007-10-31 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 15:40 [PATCH 1/8] scsi: megaraid_sas - add hibernation support bo yang
[not found] ` <9738BCBE884FDB42801FAD8A7769C265010A0A09@NAMAIL1.ad.lsil.com>
2007-10-30 17:18 ` James Bottomley
[not found] ` <9738BCBE884FDB42801FAD8A7769C265010A0A11@NAMAIL1.ad.lsil.com>
2007-10-31 17:12 ` James Bottomley [this message]
2008-04-29 7:55 ` [PATCH 1/1] scsi: megaraid_sas - Update the Version and Changelog bo yang
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 15:02 [PATCH 1/8] scsi: megaraid_sas - add hibernation support bo yang
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=1193850744.3411.69.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=Bo.Yang@lsi.com \
--cc=Neela.Kolli@lsi.com \
--cc=Sumant.Patro@lsi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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