Re: [hwloc-devel] P#0 -> P0 for logical numbers?
With p/l prefixes: € lstopo -p - Machine(993MB) + Socketp0 + L2(2048KB) L1(32KB) + Corep0 + Pp0 L1(32KB) + Corep1 + Pp1 € lstopo - Machine(993MB) + Socketl0 + L2l0(2048KB) L1l0(32KB) + Corel0 + Pl0 L1l1(32KB) + Corel1 + Pl1 What I dislike is that this seems to bring odd words like "Corel". I'd rather read this: € lstopo -p - Machine(993MB) + Socket p#0 + L2(2048KB) L1(32KB) + Core p#0 + P p#0 L1(32KB) + Core p#1 + P p#1 € lstopo - Machine(993MB) + Socket l#0 + L2 l#0(2048KB) L1 l#0(32KB) + Core l#0 + P l#0 L1 l#1(32KB) + Core l#1 + P l#1 or that: € lstopo -p - Machine(993MB) + Socket p0 + L2(2048KB) L1(32KB) + Core p0 + P p0 L1(32KB) + Core p1 + P p1 € lstopo - Machine(993MB) + Socket l0 + L2 l0(2048KB) L1 l0(32KB) + Core l0 + P l0 L1 l1(32KB) + Core l1 + P l1 Samuel
Re: [hwloc-devel] P#0 -> P0 for logical numbers?
On Jan 28, 2010, at 9:31 AM, Jeff Squyres (jsquyres) wrote: > How about 0p for physical, such as Core0p? The "#" doesn't really mean > / connote anything. > > - > € lstopo -p - > Machine(993MB) + Socket0p + L2(2048KB) > L1(32KB) + Core0p + P0p > L1(32KB) + Core1p + P1p > € lstopo - > Machine(993MB) + Socket0 + L2(2048KB) > L10(32KB) + Core0 + P0 > L11(32KB) + Core1 + P1 > - The more I look at a suffix of "p", the less I like it. :-\ I'm still not a fan of the "#" because it doesn't really mean / connote anything, but I do like the idea of some kind of a prefix better than a single-letter-suffix. Some other random ideas: - Print physical IDs in hex (doesn't necessarily connote "physical", either) Example: Core0p1 + P0x1 - Prefix with capitol P Example: CoreP1 + PP1 - Prefix with "0p", but still use decimal Example: Core0p1 + P0p1 - ...? -- Jeff Squyres jsquy...@cisco.com
Re: [hwloc-devel] P#0 -> P0 for logical numbers?
Jeff Squyres wrote: > On Jan 28, 2010, at 9:05 AM, Samuel Thibault wrote: > > >> Since we changed the default behavior of lstopo to display logical >> numbers instead of physical numbers, I've quite a few times taken one >> for the other, leading to confusion. >> > > Mmm... good point. > > >> I agree on the fact that it's >> better to have coherency, but maybe we could change the output of lstopo >> to distinguish between physical and logical? I.e. for instance >> >> € lstopo -p - >> Machine(993MB) + Socket#0 + L2(2048KB) >> L1(32KB) + Core#0 + P#0 >> L1(32KB) + Core#1 + P#1 >> € lstopo - >> Machine(993MB) + Socket0 + L20(2048KB) >> L10(32KB) + Core0 + P0 >> L11(32KB) + Core1 + P1 >> > > How about 0p for physical, such as Core0p? The "#" doesn't really mean > / connote anything. > I'd vote for just replacing # with another special character such as - or : or / when displaying logical indexes. Those are not very nice, but that's the best I have on my keyboard :) € lstopo - Machine(993MB) + Socket0 + L20(2048KB) L1:0(32KB) + Core:0 + P0 L1:1(32KB) + Core:1 + P1 € lstopo - Machine(993MB) + Socket0 + L20(2048KB) L1-0(32KB) + Core-0 + P0 L1-1(32KB) + Core-1 + P1 I think it's better to always have a special character between the type (which sometimes ends with a digit) and the index. Brice
Re: [hwloc-devel] P#0 -> P0 for logical numbers?
On Jan 28, 2010, at 9:05 AM, Samuel Thibault wrote: > Since we changed the default behavior of lstopo to display logical > numbers instead of physical numbers, I've quite a few times taken one > for the other, leading to confusion. Mmm... good point. > I agree on the fact that it's > better to have coherency, but maybe we could change the output of lstopo > to distinguish between physical and logical? I.e. for instance > > € lstopo -p - > Machine(993MB) + Socket#0 + L2(2048KB) > L1(32KB) + Core#0 + P#0 > L1(32KB) + Core#1 + P#1 > € lstopo - > Machine(993MB) + Socket0 + L20(2048KB) > L10(32KB) + Core0 + P0 > L11(32KB) + Core1 + P1 How about 0p for physical, such as Core0p? The "#" doesn't really mean / connote anything. - € lstopo -p - Machine(993MB) + Socket0p + L2(2048KB) L1(32KB) + Core0p + P0p L1(32KB) + Core1p + P1p € lstopo - Machine(993MB) + Socket0 + L20(2048KB) L10(32KB) + Core0 + P0 L11(32KB) + Core1 + P1 - Ooo -- how about roman numerals for physical? - € lstopo -p - Machine(993MB) + SocketIIV + L2(2048KB) L1(32KB) + CoreX + PXI L1(32KB) + CoreXI + PXI - Drat; Roman numerals have no "0". So -- scratch that... ;-) -- Jeff Squyres jsquy...@cisco.com
