From: Greg KH <greg@kroah.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Nathan Lynch <ntl@pobox.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Is sysfs the right place to get cache and CPU topology info?
Date: Wed, 2 Jul 2008 11:51:45 -0700 [thread overview]
Message-ID: <20080702185145.GB20938@kroah.com> (raw)
In-Reply-To: <486B9B3A.4060709@firstfloor.org>
On Wed, Jul 02, 2008 at 05:14:02PM +0200, Andi Kleen wrote:
> Nathan Lynch wrote:
> > Andi Kleen wrote:
> >> Andrew Morton <akpm@linux-foundation.org> writes:
> >>> sysfs is part of the kernel ABI. We should design our interfaces there
> >>> as carefully as we design any others.
> >> The basic problem is that sysfs exports an internal kernel object model
> >> and these tend to change. To really make it stable would require
> >> splitting it into internal and presented interface.
> >
> > True, but... /sys/devices/system/cpu has been there since around 2.6.5
> > iirc. A google code search for that path shows plenty of programs
> > (including hal) that hard-code it. Exposed object model or not,
> > changing that path would break lots of software.
>
> Yes it would.
>
> But Greg is making noises of getting rid of sysdevs and it wouldn't
> surprise me if that ended up being user visible since most object
> model changes end up being visible.
I hope to make sysdevs go away in such a manner that the sysfs tree does
not change at all. That's my goal, but we still have a long ways to go
before we can even consider attempting to do this, so don't worry about
putting things in this location if you feel it is the best fit.
thanks,
greg k-h
next prev parent reply other threads:[~2008-07-02 18:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 6:27 Is sysfs the right place to get cache and CPU topology info? Paul Mackerras
2008-07-02 7:37 ` Andrew Morton
2008-07-02 9:45 ` Paul Mackerras
2008-07-02 10:01 ` Andrew Morton
2008-07-02 11:46 ` Paul Mackerras
2008-07-02 16:47 ` Andrew Morton
2008-07-02 11:12 ` Andi Kleen
2008-07-02 14:35 ` Nathan Lynch
2008-07-02 15:14 ` Andi Kleen
2008-07-02 18:51 ` Greg KH [this message]
2008-07-02 21:41 ` Removing sysdevs? (was: Re: Is sysfs the right place to get cache and CPU topology info?) Rafael J. Wysocki
2008-07-02 21:48 ` Greg KH
2008-07-02 21:57 ` Removing sysdevs? Andi Kleen
2008-07-02 22:15 ` Greg KH
2008-07-03 9:53 ` Andi Kleen
2008-07-04 1:09 ` Greg KH
2008-07-02 22:17 ` Benjamin Herrenschmidt
2008-07-02 22:08 ` Removing sysdevs? (was: Re: Is sysfs the right place to get cache and CPU topology info?) Rafael J. Wysocki
2008-07-02 22:16 ` Greg KH
2008-07-02 23:06 ` Rafael J. Wysocki
2008-07-02 17:08 ` [PATCH] sysfs-rules.txt: reword API stability statement Nathan Lynch
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=20080702185145.GB20938@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox