Please be sure to look at
A few people on this list probably have looked at it
--- Samuel Ortiz <sortiz@...> wrote:
> I am curently working on making the kernel aware of
> the distances that
> exist, in NUMA architectures, between cpus and
> memories. I would like to
> build a matrix of distances between each cpus and
> memory chunk, but I have
> some hesitations here.
> I would also like these distances to be readable
> from the /proc
> Since I'm assuming that may be some of you are
> interested or even working
> on the same problem, and that it would be much
> better to agree on some
> points before going further, I need your advices,
> ideas, or feedback.
> I have basically three questions about it:
> 1) The term distance, in my opinion, refers to hops
> distances, but I
> would like to know if everybody agrees on that, or
> if someone out there
> thinks that another unit (miliseconds, Mo/s, or
> anything else) would be
> better and more useful.
> 2) I'm not sure at all wether building a generic
> cpu<->memory distance
> matrix, or a more architecture dependent matrix,
> which for the SGI case
> would be a node<->node distance matrix. I think a
> node<->node matrix would
> make more sense, since this is not that architecture
> node<->node for SGI, quad<->quad for some others,
> but basically the
> same concept.
> 3) Concerning the /proc filesystem, I think it would
> be nice to agree on a
> "standard" directory structure and information
> displaying. Something like
> file per each
> node/quad/anything similar , containing the
> distances between these node
> and the other, may be fine. I'm not sure at all
> neither though...
> I would really appreciate your help/feedback on that
> points, and on
> anything related to this distances matrix.
> Samuel Ortiz
> SGI, Intern.
> Ecole des Mines de Paris, FRANCE
> Lse-tech mailing list
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail