From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: colpatch@us.ibm.com, linux-kernel@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [RFC] pci_bus conversion to struct device
Date: Wed, 17 Jan 2007 19:31:45 -0800 [thread overview]
Message-ID: <20070118033145.GA16368@kroah.com> (raw)
In-Reply-To: <20070118022352.GA17531@parisc-linux.org>
On Wed, Jan 17, 2007 at 07:23:52PM -0700, Matthew Wilcox wrote:
> On Wed, Jan 17, 2007 at 04:53:45PM -0800, Greg KH wrote:
> > I'm trying to clean up all the usages of struct class_device to use
> > struct device, and I ran into the pci_bus code. Right now you create a
> > symlink called "bridge" under the /sys/class/pci_bus/XXXX:XX/ directory
> > to the pci device that is the bridge.
>
> I recommend we just delete the pci_bus class. I don't think it serves
> any useful purpose. The bridge can be inferred frmo the sysfs hierarchy
> (not to mention lspci will tell you). The cpuaffinity file should be
> moved from the bus to the device -- it really doesn't make any sense to
> talk about which cpu a bus is affine to, only a device.
I would like to do that, but I want to make sure that no userspace tools
are using this information.
But, as Matt Dobson is now gone off somewhere in Europe, not doing Linux
stuff anymore, he's not going to answer this. So I'll just make up a
removal patch and let it sit in -mm for a while to see if anything
breaks.
I really only think the big NUMA boxes care about that information, if
anything.
thanks,
greg k-h
next prev parent reply other threads:[~2007-01-18 3:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 0:53 [RFC] pci_bus conversion to struct device Greg KH
2007-01-18 2:23 ` Matthew Wilcox
2007-01-18 3:31 ` Greg KH [this message]
2007-01-18 8:14 ` Martin Mares
2007-01-18 9:00 ` Greg KH
2007-01-18 18:23 ` Jesse Barnes
2007-01-18 21:01 ` Martin Mares
2007-01-24 0:22 ` Tim Pepper
2007-01-24 0:47 ` Benjamin Herrenschmidt
2007-01-27 16:19 ` Matthew Wilcox
2007-01-29 19:13 ` Jesse Barnes
2007-01-19 6:58 ` Grant Grundler
2007-01-27 16:16 ` Matthew Wilcox
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=20070118033145.GA16368@kroah.com \
--to=greg@kroah.com \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=matthew@wil.cx \
/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