Re: /proc/cpuinfo format - arch dependent!

[Stefan Smietanowski <stesmi@stesmi.com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

> I personally think that what would be useful is not "the number of CPUs"
> (which does not make any sense), but an enumeration of :
> 
>     - the physical nodes (for NUMA)
>     - the physical CPUs
>     - each CPU's cores (for multi-core)
>     - each core's siblings (for HT/SMT)
> 
> each of which would report their respective id for {set,get}_affinity().
> This way, the application would be able to choose how it needs to spread
> over available CPUs depending on its workload. But IMHO, this should
> definitely not be put in cpuinfo. I consider that cpuinfo is for the human.

When one defines it one way you can be sure there'll come some company
and figure something out that doesn't fit into that representation.

Like - Stick a board into the CPU slot of some motherboard. That board
has two DualCore, SMT chips.

Oops.

Now the funny part - there is a company selling those things (not
dualcore yet, but SMT anyhow).

How do you fit it into that model?

// Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iD8DBQFCfQDoBrn2kJu9P78RAtUSAJ42Jm9xbpOE9UhOP7kpj5vGTuiPbACfXiB5
PnjLvgytXnlnrlKO+IVW5GE=
=ovm/
-----END PGP SIGNATURE-----
-
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/