linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: Greg KH <greg@kroah.com>
Cc: Keiichiro Tokunaga <tokunaga.keiich@jp.fujitsu.com>,
	lhcs-devel@lists.sourceforge.net,
	lhms-devel@lists.sourceforge.net,
	linux-hotplug-devel@lists.sourceforge.net,
	pcihpd-discuss@lists.sourceforge.net,
	lhns-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	acpi-largesys-devel@lists.sourceforge.net
Subject: Re: [Pcihpd-discuss] [RFC] New sysfs tree for hotplug
Date: Fri, 16 Apr 2004 23:39:44 +0000	[thread overview]
Message-ID: <20040416233944.GF24556@cup.hp.com> (raw)
In-Reply-To: <20040416223436.GB21701@kroah.com>

On Fri, Apr 16, 2004 at 03:34:36PM -0700, Greg KH wrote:
> >  Recent large machines have many PCI devices and some boards that
> > contain devices (e.g. CPU, memory, and/or I/O devices).  A certain PCI
> > device (PCI1) might be connected with other one (PCI2), which means that
> > there is a dependency between PCI1 and PCI2.
> 
> You have this today?

I interpreted his comments to mean PCI-PCI Bridges.
eg something like a 4-port NIC which usually has a PCI-PCI bridge
to "isolate" multiple PCI devices (NICs):
 +-[60]---01.0-[61]--+-04.0  Digital Equipment Corporation DECchip 21142/43
 |                   +-05.0  Digital Equipment Corporation DECchip 21142/43
 |                   +-06.0  Digital Equipment Corporation DECchip 21142/43
 |                   \-07.0  Digital Equipment Corporation DECchip 21142/43
...

I thought this was already handled though so I may be misunderstanding.
Keiichiro, an example would be very helpful in understanding.

...
> Hm, no.  What about usb, firewire, scsi and any other future bus that
> can be "hotpluggable".  The kernel doesn't treat them differently, and
> we shouldn't either.

SCSI has a heirarchy as well. Ie LUNs can be removed without
removing the target (RAID controllers). Normal JBOD use equates
LUNs and targets.

grant


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15  8:09 [RFC] New sysfs tree for hotplug Keiichiro Tokunaga
2004-04-16 22:34 ` [Pcihpd-discuss] " Greg KH
2004-04-16 23:39   ` Grant Grundler [this message]
2004-04-23 12:21     ` Keiichiro Tokunaga
2004-04-23 12:18   ` Keiichiro Tokunaga
2004-04-23 12:30     ` Matthew Wilcox
2004-04-23 12:47     ` Matthew Wilcox
2004-04-23 20:07     ` Greg KH

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=20040416233944.GF24556@cup.hp.com \
    --to=iod00d@hp.com \
    --cc=acpi-largesys-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=lhcs-devel@lists.sourceforge.net \
    --cc=lhms-devel@lists.sourceforge.net \
    --cc=lhns-devel@lists.sourceforge.net \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    --cc=tokunaga.keiich@jp.fujitsu.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).