public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: "Smart, James" <James.Smart@Emulex.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
	Linux SCSI Reflector <linux-scsi@vger.kernel.org>
Subject: RE: Attributes
Date: 16 Apr 2004 10:15:17 -0500	[thread overview]
Message-ID: <1082128518.2130.13.camel@mulgrave> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF2802C0169D@xbl.ma.emulex.com>

On Fri, 2004-04-16 at 10:03, Smart, James wrote:
> I've considered the daemon approach (using sysfs) - but didn't believe it
> applied for a value that had to be set at boot time (when the link first
> initializes). For boot, the thought is to either compile it in, or perhaps
> get it via a module parameter assuming module.conf get copied into the
> inital ram disk.

Not at all.  All that happens is that you have to run the daemon before
using the devices.  So you'd need an initramfs/initrd daemon but *only*
if your root device is on a fibre whose topology you want to control.

> This brings up another question...  assuming a driver gets into the kernel
> tree, but it has an associated user-space entity like this daemon. How does
> one get the user-space elements onto the different distributions in concert
> with the kernel ?  (other than lobbying each distribution individually ?)

One publishes the user space entries separately.  The distributions
necessarily pick them up if they want the driver to work correctly.

James



  reply	other threads:[~2004-04-16 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 15:03 Attributes Smart, James
2004-04-16 15:15 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-16 13:55 Attributes Smart, James
2004-04-16 14:26 ` Attributes James Bottomley
2004-04-12 16:43 Attributes Smart, James
2004-04-16 12:03 ` Attributes Christoph Hellwig

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=1082128518.2130.13.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=James.Smart@Emulex.com \
    --cc=hch@infradead.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