From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, mochel@osdl.org
Subject: Re: [PATCH] eliminate pci_dev name
Date: Thu, 14 Nov 2002 14:10:27 -0500 [thread overview]
Message-ID: <3DD3F523.4000601@pobox.com> (raw)
In-Reply-To: <3DD3EB3D.8050606@pobox.com>
Matthew Wilcox wrote:
> On Thu, Nov 14, 2002 at 10:36:03AM -0800, Linus Torvalds wrote:
>
> >Actually, I think we should do the reverse (for testing), and make the
> >name be something small like 8 bytes, and make sure that everybody who
> >writes the name uses strncpy() and snprintf() instead of just blindly
> >writing whatever is in the database.
> >
> >Otherwise we'll always end up having fragile magic constants.
> >
> >Anybody willing to do that cleanup?
>
>
> Sure, I can do that. That leads me to think that maybe we should
> delete name from struct device and just use the one in struct kobject
> (which is already a mere 16 bytes). But if we're going to go as far
> down as the kobject... that has a dentry. And dentrys have names.
> So how about eliminating that too and just creating a dentry with the
> almost infinitely long name?
Remember that the names we are talking about here is the English
descriptive name of the PCI device... there is only _one_ need for
these names: /proc/pci
If there is going to be this much thought put into it (what a waste of
brain cycles <g>), then let's just remove CONFIG_PCI_NAMES and the name
field completely. lspci prints them out from its own database anyway,
and the only _real_ use is to provide descriptive names for devices in
/proc/pci. Why bother? For existing code, just use pdev->slot_name
instead, which is what happens anyway for hotplugged devices that appear
after we drop the PCI name database during the __init phase.
Comments?
Jeff
prev parent reply other threads:[~2002-11-14 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 17:10 [PATCH] eliminate pci_dev name Matthew Wilcox
2002-11-14 18:28 ` Jeff Garzik
2002-11-14 18:34 ` Matthew Wilcox
2002-11-14 18:36 ` Linus Torvalds
2002-11-14 18:44 ` Matthew Wilcox
2002-11-14 19:22 ` Linus Torvalds
2002-11-14 20:44 ` Ingo Oeser
2002-11-16 23:47 ` Matthew Wilcox
2002-11-14 19:10 ` Jeff Garzik [this message]
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=3DD3F523.4000601@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@transmeta.com \
--cc=willy@debian.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.