From: Jeff Garzik <jgarzik@pobox.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: /proc/pci deprecation?
Date: Fri, 06 Dec 2002 17:17:01 -0500 [thread overview]
Message-ID: <3DF121DD.6070206@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212061506060.1010-100000@localhost.localdomain>
Patrick Mochel wrote:
> ISTR /proc/pci being deprecated at one point in the past. It may have only
> been discussed, though. In which case, is it possible to deprecate it?
> lscpi(8) is considered a superior means to derive the same information.
>
> Elimination of it would eliminate a chunk of code in drivers/pci/proc.c,
> and obviate the use of struct device::name by the PCI layer. This change
> would probably allow us to remove the name field altogether, since PCI is
> the only code that really relies on it (and only for /proc/pci AFAICT).
Historically, this was a Linus call :)
IIRC it was one of (a) deprecated, (b) removed, or (c) almost removed in
the past, and Linus un-deprecated it. The logic back then was that it
provides a quick summary of a lot of useful info, a la /proc/cpuinfo and
/proc/meminfo. i.e. you don't need lspci installed, just been /bin/cat.
Personally, I think it would be nice to eliminate /proc/pci -- in favor
of something that provides similar functionality from sysfs: "cat
/sys/all-busses" or somesuch. I dunno how feasible that is. The main
idea is to list as many attached devices as possible in one go, without
having to cat 40 different files :) [unfortunately I think this means I
am disagreeing with you ;)]
I do grant you it would make various __init sections and in-memory
structures smaller if we eliminated the names... do we want to? Sure
we have lseisa and lspci and lsusb, et. al. Does that obviate the need
for a simple summary of attached hardware?
Jeff
next prev parent reply other threads:[~2002-12-06 22:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 21:13 /proc/pci deprecation? Patrick Mochel
2002-12-06 22:17 ` Jeff Garzik [this message]
2002-12-06 22:13 ` Patrick Mochel
2002-12-07 16:23 ` Krzysztof Halasa
2002-12-07 21:18 ` Kai Henningsen
2002-12-08 20:01 ` Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 23:18 Petr Vandrovec
2002-12-07 7:44 ` Willy Tarreau
2002-12-07 13:20 ` Tomas Szepe
2002-12-07 19:03 ` Linus Torvalds
2002-12-08 2:56 ` Patrick Mochel
2002-12-08 4:21 ` Linus Torvalds
2002-12-08 20:56 ` Richard Henderson
2002-12-09 1:54 ` Linus Torvalds
2002-12-09 3:59 ` Patrick Mochel
2002-12-09 13:35 ` Ivan Kokshaysky
2002-12-09 14:11 ` Alan Cox
2002-12-09 17:00 ` Linus Torvalds
2002-12-09 18:29 ` Alan Cox
2002-12-09 18:11 ` Linus Torvalds
2002-12-09 18:16 ` Jeff Garzik
2002-12-10 0:43 ` Alan Cox
2002-12-10 0:30 ` Linus Torvalds
2002-12-10 5:57 ` Eric W. Biederman
2002-12-09 23:27 ` Vojtech Pavlik
2002-12-09 14:14 ` Alan Cox
2002-12-10 16:42 ` Martin Mares
2002-12-07 12:35 ` Erik Hensema
2002-12-07 13:15 ` Dr. David Alan Gilbert
2002-12-07 17:46 ` Arnaldo Carvalho de Melo
2002-12-09 19:03 ` Rogier Wolff
2002-12-09 19:08 ` Arnaldo Carvalho de Melo
2002-12-07 13:14 ` Tomas Szepe
2002-12-07 18:52 ` Petr Vandrovec
2002-12-08 12:30 ` Erik Hensema
2002-12-09 10:14 ` Geert Uytterhoeven
2002-12-09 9:15 Adam J. Richter
2002-12-09 11:00 Nicolas Mailhot
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=3DF121DD.6070206@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.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