From: Andi Kleen <ak@suse.de>
To: Zan Lynx <zlynx@acm.org>
Subject: Re: Wrong number of core_siblings in sysfs for Athlon64 X2
Date: Fri, 17 Feb 2006 03:18:15 +0100
User-Agent: KMail/1.8.2
Cc: Jesper Juhl <jesper.juhl@gmail.com>, LKML <linux-kernel@vger.kernel.org>,
       Greg Kroah-Hartman <gregkh@suse.de>
References: <9a8748490602161346x6e2802e8r4edf7dcbdafa5e17@mail.gmail.com> <9a8748490602161408i736a7ab3vef09f3e1c95916fe@mail.gmail.com> <1140142257.29021.31.camel@localhost>
In-Reply-To: <1140142257.29021.31.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200602170318.15511.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1015
Lines: 25

On Friday 17 February 2006 03:10, Zan Lynx wrote:

> It seems to me that this could be confusing for a lot of people who are
> casually browsing through sysfs.  Why not name core_siblings something
> like core_sibling_bitmap? 

Because it's already a fixed ABI that is put in stone.

The only way to do what you want would be to add a new field
and keep the old one alone, but frankly your rationale for 
it ("could be confusing to someone") doesn't seem convincing enough 
for such a thing.  Especially since each sysfs field can
cost considerable memory when a dentry and a inode have to be allocated
for it.

I guess if you worry about such people a better way to help
them would be to write them a frontend that displays
the information in there in nice form.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/