mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Lundell <jlundell@pobox.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] adding PCI bus information to SCSI layer
Date: Tue, 24 Apr 2001 16:16:39 -0700	[thread overview]
Message-ID: <p05100313b70bb73ce962@[207.213.214.37]> (raw)
In-Reply-To: <200104242159.f3OLxoB07000@vindaloo.ras.ucalgary.ca>
In-Reply-To: <CDF99E351003D311A8B0009027457F140810E286@ausxmrr501.us.dell.com> <200104242159.f3OLxoB07000@vindaloo.ras.ucalgary.ca>

At 3:59 PM -0600 4/24/01, Richard Gooch wrote:
>The plan I have (which I hope to get started on soon, now that I'm
>back from travels), is to change /dev/scsi/host# from a directory into
>a symbolic link to a directory called: /dev/bus/pci0/slot1/function0.
>Thus, to access a partition via location, one would use the path:
>/dev/bus/pci0/slot1/function0/bus0/target1/lun2/part3.

A minor PCI terminology point: PCI buses are subdivided into devices, not (necessarily) slots. So, for example, a multiple-device PCI card (say, two SCSI controllers) might have a PCI bridge creating a new bus, and two devices (not slots) on that bus. (It could alternatively be implemented as a single device with two functions,  given a dual-interface chip, but not necessarily.)

So a better name would be /dev/bus/pci0/dev1/fcn0/bus0/tgt1/lun2/part3 (taking the liberty of abbreviating some of the other names).

How, if at all, would RAID devices, using more than one physical device, or SCSI bus, or PCI card, fit into this naming scheme?


-- 
/Jonathan Lundell.

  parent reply	other threads:[~2001-04-24 23:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 21:02 Matt_Domsch
2001-04-24 21:59 ` Richard Gooch
2001-04-27  4:31   ` Richard Gooch
2001-05-01  1:27     ` Richard Gooch
2001-05-01  8:46       ` Ingo Oeser
2001-05-01 16:53       ` Richard Gooch
2001-05-01 20:32         ` Alan Cox
2001-05-02 15:03           ` Ingo Oeser
2001-05-02 15:54             ` Alan Cox
2001-05-03  8:57           ` Chris Wedgwood
2001-05-03  9:49             ` Alan Cox
2001-05-03 10:23               ` Chris Wedgwood
2001-04-24 23:16 ` Jonathan Lundell [this message]
2001-04-27  5:24   ` Jonathan Lundell
2001-05-01 14:38     ` Jonathan Lundell
2001-05-03  7:32     ` Kai Henningsen
2001-05-03  7:51     ` Jonathan Lundell
2001-05-11 16:32       ` Ralf Baechle
2001-05-11 23:00         ` Steven Willoughby
2001-05-11 22:49       ` Jonathan Lundell
2001-05-12  2:20         ` Ralf Baechle
2001-05-12  4:21         ` Jonathan Lundell
     [not found] <p0510030db7221c090810@[10.128.7.49]=FE2>
2001-05-12 11:00 ` Kai Henningsen

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='p05100313b70bb73ce962@[207.213.214.37]' \
    --to=jlundell@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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

all inboxes | Powered by JetHome®