linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "Bagalkote, Sreenivas" <sreenib@lsil.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/2] RE: How to add/drop SCSI drives from within the drive r?
Date: Thu, 9 Dec 2004 22:15:55 -0600	[thread overview]
Message-ID: <20041210041555.GA9972@lists.us.dell.com> (raw)
In-Reply-To: <1102645481.3814.5.camel@mulgrave>

On Thu, Dec 09, 2004 at 08:24:41PM -0600, James Bottomley wrote:
> On Thu, 2004-12-09 at 20:21 -0500, Bagalkote, Sreenivas wrote:
> > +i.	Introduced driver ioctl that returns scsi address for a given ld.
> > +	
> > +	"Why can't the existing sysfs interfaces be used to do this?"
> > +		- Brian King (brking@us.ibm.com)
> > +	
> > +	"I've looked into solving this another way, but I cannot see how
> > +	to get this driver-private mapping of logical drive number-> HCTL
> > +	without putting code something like this into the driver."
> 
> OK now I look at the code, I have another suggestion.  Why not simply
> publish the logical drive number as an extra file in the device sysfs
> directory?  That way you can get your C:H:T:L, go to the end of the tree
> and cat megaraid_sd (or whatever you want to call it).

That works in the delete case, but doesn't work in the add case,
because there's no SCSI device created (yet) to have a sysfs directory
to put the file to get the information userspace needs to call
../../scan.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

      reply	other threads:[~2004-12-10  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  1:21 [PATCH 2/2] RE: How to add/drop SCSI drives from within the drive r? Bagalkote, Sreenivas
2004-12-10  2:24 ` James Bottomley
2004-12-10  4:15   ` Matt Domsch [this message]

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=20041210041555.GA9972@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sreenib@lsil.com \
    /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;
as well as URLs for NNTP newsgroup(s).