From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: albert@users.sourceforge.net, linux-kernel@vger.kernel.org,
bcollins@debian.org, wli@holomorphy.com, tom_gall@vnet.ibm.com,
anton@samba.org
Subject: Re: /proc/bus/pci
Date: Wed, 04 Jun 2003 22:01:17 -0700 (PDT) [thread overview]
Message-ID: <20030604.220117.26306541.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306042117440.2761-100000@home.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Wed, 4 Jun 2003 21:23:16 -0700 (PDT)
On Wed, 4 Jun 2003, Albert Cahalan wrote:
> bus/pci/00/00.0 -> ../hose0/bus0/dev0/fn0/config-space
Why do we have that stupid "hose" name? Only because of strange alpha
naming, or did somebody else also use that incredibly silly name?
Please talk about "domains", at least it makes some sense as a name.
I agree.
I'm also hoping that /proc/bus will eventually go away, so I don't
see a major problem with not understanding multiple domains at that
level.
On a /sys/bus/xxx level we actually should already be able to handle
multiple domains, but the naming is broken. However, in /sys we should be
able to nicely handling non-zero domains by just extending the name space
a bit.
My only concern is what file lookup algorithm we should be encouraging
things like xfree86 to use. Check /sys then /proc/bus?
next prev parent reply other threads:[~2003-06-05 4:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 3:21 /proc/bus/pci Albert Cahalan
2003-06-05 3:35 ` /proc/bus/pci William Lee Irwin III
2003-06-05 4:23 ` /proc/bus/pci Linus Torvalds
2003-06-05 5:01 ` David S. Miller [this message]
2003-06-05 12:05 ` /proc/bus/pci Albert Cahalan
2003-06-05 12:16 ` /proc/bus/pci David S. Miller
2003-06-05 12:42 ` /proc/bus/pci Albert Cahalan
2003-06-05 12:36 ` /proc/bus/pci Albert Cahalan
2003-06-05 15:51 ` /proc/bus/pci Linus Torvalds
2003-06-05 16:00 ` /proc/bus/pci William Lee Irwin III
2003-06-05 17:23 ` /proc/bus/pci Benjamin Herrenschmidt
2003-06-05 17:36 ` /proc/bus/pci William Lee Irwin III
2003-06-05 17:18 ` /proc/bus/pci Riley Williams
2003-06-06 16:30 ` /proc/bus/pci Ross Biro
2003-06-06 18:13 ` /proc/bus/pci Riley Williams
2003-06-07 2:02 ` /proc/bus/pci Horst von Brand
2003-06-07 0:25 ` /proc/bus/pci Robert White
2003-06-07 0:35 ` /proc/bus/pci Linus Torvalds
2003-06-07 1:01 ` /proc/bus/pci Robert White
2003-06-07 1:43 ` /proc/bus/pci Albert Cahalan
2003-06-05 12:43 ` /proc/bus/pci Benjamin Herrenschmidt
2003-06-05 16:58 ` /proc/bus/pci Greg KH
2003-06-05 18:27 ` /proc/bus/pci Matt Wilson
2003-06-05 19:35 ` /proc/bus/pci Greg KH
[not found] <20030605125013$41ac@gated-at.bofh.it>
[not found] ` <20030605160017$10e1@gated-at.bofh.it>
2003-06-05 16:41 ` /proc/bus/pci Julien Oster
2003-06-05 16:57 ` /proc/bus/pci Mike Dresser
2003-06-05 17:00 ` /proc/bus/pci Richard B. Johnson
2003-06-07 0:31 ` /proc/bus/pci Robert White
2003-06-05 20:49 ` /proc/bus/pci Michal Jaegermann
2003-06-12 4:29 ` /proc/bus/pci Andre Hedrick
2003-06-13 7:10 ` /proc/bus/pci Riley Williams
2003-06-13 8:43 ` /proc/bus/pci Olivier Galibert
2003-06-13 16:28 ` /proc/bus/pci Mr. James W. Laferriere
2003-06-13 17:59 ` /proc/bus/pci Riley Williams
2003-06-13 19:37 ` /proc/bus/pci Mr. James W. Laferriere
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 17:03 /proc/bus/pci Grover, Andrew
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=20030604.220117.26306541.davem@redhat.com \
--to=davem@redhat.com \
--cc=albert@users.sourceforge.net \
--cc=anton@samba.org \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom_gall@vnet.ibm.com \
--cc=torvalds@transmeta.com \
--cc=wli@holomorphy.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