Open MPI logo

Hardware Locality Users' Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-users] Magny Cours L3 cache issue
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2011-08-16 11:01:29

Wheeler, Kyle Bruce, le Tue 16 Aug 2011 16:52:54 +0200, a écrit :
> On Aug 15, 2011, at 4:14 PM, Samuel Thibault wrote:
> > Wheeler, Kyle Bruce, le Tue 16 Aug 2011 00:11:41 +0200, a écrit :
> >> I'm having the problem that my Magny Cours system is being identified (via hwloc-ls) as sharing an L3 cache between the NUMAnodes on a single socket. I know that this is not actually true, and I don't know how to begin debugging hwloc to see why it thinks that about the L3 cache. Thoughts?
> >
> > I guess you have updated to the latest Linux kernel version?
> Unfortunately, this is not on a machine I have root access to. But, for what it's worth, here's the uname -a output:
> Linux mzlogin01e #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux

This is quite old indeed, I'm not surprised that there are topology
detection issues on it. And our x86 backend will probably not help since
it's not NUMA-aware.