lkml.org 
[lkml]   [2006]   [Feb]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Wrong number of core_siblings in sysfs for Athlon64 X2
Date
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/

\
 
 \ /
  Last update: 2006-02-17 03:20    [W:1.155 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site