From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
"Bagalkote, Sreenivas" <sreenib@lsil.com>,
brking@us.ibm.com, Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
bunk@fs.tum.de, Andrew Morton <akpm@osdl.org>,
"Ju, Seokmann" <sju@lsil.com>,
"Doelfel, Hardy" <hdoelfel@lsil.com>,
"Mukker, Atul" <Atulm@lsil.com>
Subject: Re: How to add/drop SCSI drives from within the driver?
Date: Wed, 15 Dec 2004 13:49:18 -0500 [thread overview]
Message-ID: <1103136559.5232.1.camel@mulgrave> (raw)
In-Reply-To: <20041215072453.GB17274@lists.us.dell.com>
On Wed, 2004-12-15 at 01:24 -0600, Matt Domsch wrote:
> James, I've been thinking about this a little more, and you may be on
> to something here. Let each driver add files as such:
>
> /sys/class/scsi_host
> |-- host0
> | |-- add_logical_drive
> | |-- remove_logical_drive
> | `-- rescan_logical_drive
>
> Then we can go 2 ways with this.
> 1) driver functions directly call scsi_add_device(),
> scsi_remove_device(), and something for rescan (option 2 handles this
> one cleanly for us). ATM, megaraid_mbox doesn't implement a rescan
> function, so this point may be moot.
>
> 2) driver functions call a midlayer library function, which invokes
> /sbin/hotplug with appropriate data, and add a new /etc/hotplug.d
> helper app which would then write to these files:
>
> /sys/class/scsi_host
> |-- host0
> | |-- scan
> /sys/devices/pci0000:0x/0000:0x:0x.0/host0
> |-- 0:0:0:0
> | |-- delete
> | |-- rescan
>
> to do likewise.
I'll buy this (option 2).. it seems like a good way to export the
megaraid specific information and at the same time integrate it more
fully into the evolving hotplug infrastructure.
James
next prev parent reply other threads:[~2004-12-15 20:28 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 18:42 How to add/drop SCSI drives from within the driver? Salyzyn, Mark
2004-12-08 20:01 ` James Bottomley
2004-12-15 7:24 ` Matt Domsch
2004-12-15 16:48 ` Matt Domsch
2004-12-15 18:55 ` James Bottomley
2004-12-15 18:49 ` James Bottomley [this message]
2004-12-15 21:30 ` Matt Domsch
2004-12-16 9:54 ` Arjan van de Ven
2004-12-16 14:41 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 23:23 Mukker, Atul
2005-01-27 7:05 ` 'Patrick Mansfield'
2005-01-26 16:48 Greg KH
2005-01-25 23:37 Mukker, Atul
2005-01-26 14:48 ` Brian King
2005-01-25 16:27 Mukker, Atul
2005-01-25 16:52 ` Patrick Mansfield
2005-01-21 22:11 Mukker, Atul
2005-01-21 23:58 ` James Bottomley
2005-01-06 14:20 Mukker, Atul
2005-01-06 14:42 ` James Bottomley
2005-01-04 17:25 Bagalkote, Sreenivas
2005-01-04 17:42 ` James Bottomley
2005-01-03 23:02 Bagalkote, Sreenivas
2005-01-03 23:40 ` James Bottomley
2004-12-16 16:51 Salyzyn, Mark
2004-12-16 14:27 Mukker, Atul
2004-12-15 19:42 Mukker, Atul
2004-12-15 20:22 ` Matt Domsch
2004-12-10 0:31 Bagalkote, Sreenivas
2004-12-09 23:37 Bagalkote, Sreenivas
2004-12-10 0:03 ` Matt Domsch
2004-12-09 17:31 Mukker, Atul
2004-12-09 18:00 ` 'Patrick Mansfield'
2004-12-09 14:11 Mukker, Atul
2004-12-09 17:04 ` Patrick Mansfield
2004-12-08 19:25 Mukker, Atul
2004-12-08 17:56 Bagalkote, Sreenivas
2004-12-08 19:06 ` James Bottomley
2004-12-08 14:55 Mukker, Atul
2004-12-08 7:16 Bagalkote, Sreenivas
2004-12-08 14:07 ` Matt Domsch
2004-12-08 15:40 ` Matthew Wilcox
2004-12-08 15:59 ` James Bottomley
2004-12-08 23:46 ` Brian King
2004-12-03 17:18 Bagalkote, Sreenivas
2004-12-03 15:29 Bagalkote, Sreenivas
2004-12-03 15:58 ` Jan-Benedict Glaw
2004-12-03 16:22 ` Christoph Hellwig
2004-12-03 17:11 ` Matt Domsch
2004-12-03 17:14 ` Matt Domsch
2004-12-03 2:04 Bagalkote, Sreenivas
2004-12-03 15:10 ` Brian King
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=1103136559.5232.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Atulm@lsil.com \
--cc=Matt_Domsch@Dell.com \
--cc=akpm@osdl.org \
--cc=brking@us.ibm.com \
--cc=bunk@fs.tum.de \
--cc=hdoelfel@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=sju@lsil.com \
--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