Hi,
From: Karel Zak <kzak@xxxxxxxxxx>
Subject: Re: [RESEND][RFC] lscpu - CPU architecture information helper
Date: Thu, 10 Jul 2008 09:59:23 +0200
> On Thu, Jul 10, 2008 at 11:14:55AM +0800, Cai Qian wrote:
> > Hi,
> >
> > From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
> > Subject: Re: [RESEND][RFC] lscpu - CPU architecture information helper
> > Date: Wed, 9 Jul 2008 11:46:32 +0100
> >
> > > Hello,
> > >
> > > Cai Qian, le Wed 09 Jul 2008 11:50:51 +0800, a écrit :
> > > > #CPU,Core,Socket,Node,L1d,L1i,L2,L3
> > > > 0,0,0,0,0,0,0,0
> > > > 1,1,1,0,1,1,1,1
> > > > 2,2,2,1,2,2,2,2
> > > > 3,3,3,1,3,3,3,3
> > >
> > > I'm wondering whether it may be a bit hard to grasp the switch from Node
> > > to L1d, maybe we should add a separator there?
> > >
> >
> > Although it maybe a little bit diffcult to match, the advantage is to
> > use CSV format and be compact. Alternatively, it could be something like
> > this,
> >
> > cpu,0,core,0,socket,0,node,0,l1d,0,l1i,0,l2,0,l3,0
> > cpu,1,core,1,socket,1,node,0,l1d,1,l1i,1,l2,1,l3,1
> > cpu,2,core,2,socket,2,node,1,l1d,2,l1i,2,l2,2,l3,2
> > cpu,3,core,3,socket,3,node,1,l1d,3,l1i,3,l2,3,l3,3
> >
> > or
> >
> > cpu,0,core,0,socket,0,node,0,l1d,0,l1i,0,l2,0,l3,0
> > ,1,,1,,1,,0,,1,,1,,1,,1
> > ,2,,2,,2,,1,,2,,2,,2,,2
> > ,3,,3,,3,,1,,3,,3,,3,,3
>
> or make it customizable:
>
> $ lscpu --columns="cpu,core,socket"
>
> or git-like solution:
>
> $ lspci --pretty=format:"%cpu %core %socket"
>
> where you can also predefine a few basic formats
> (--pretty={format,csv,...})
>
It won't be easy to do that, as cache name fields are not always
predictable. Some have separated instruction and data caches for L1 or
L2, while some do not. Also, one reason for the parsable format is to
give users sufficient information if they want to use "taskset" to run
processes on different CPUs. I probably look and see how users are
actually going to use the parsable format, and improve it in the next
version.
CaiQian
>
> Karel
>
>
> --
> Karel Zak <kzak@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
