[hwloc-devel] Cpuset problem
I was doing some testing on what's in SVN and I found that the topology discovery code has a problem when running within a cpuset. On my 2.6.32 SLES11SP1 box the code calls hwloc_read_linux_cpuset_mask() with a cgroup mount point and tries to read /dev/cpuset//cpuset.[cpus|mems]. Those files don't exist but /[cpus|mems] do. If I change the code to use those files instead then everything else works. It seems that either the formatting for cgroup files is wrong, or the code thinks it's dealing with cgroups when it's really using cpusets. -- Michael A. Raymond Message Passing Toolkit Team Silicon Graphics Inc (651) 683-3434
Re: [hwloc-devel] Cpuset problem
Le 22/07/2010 14:53, Michael Raymond a écrit : > I was doing some testing on what's in SVN and I found that the > topology discovery code has a problem when running within a cpuset. On > my 2.6.32 SLES11SP1 box the code calls hwloc_read_linux_cpuset_mask() > with a cgroup mount point and tries to read > /dev/cpuset//cpuset.[cpus|mems]. Those files don't exist but > /[cpus|mems] do. If I change the code to use those files instead > then everything else works. > Hello Michael, This probably means that we found a cgroup mount point in /dev/cpuset while its actually a cpuset mount point. What does your /proc/mounts contain? Can you try to understand why hwloc_find_linux_cpuset_mntpnt would find a wrong mount type? thanks, Brice
Re: [hwloc-devel] Cpuset problem
/proc/mounts: cpuset /dev/cpuset cgroup rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0 The third element there is "cgroup" which the code specifically looks for in hwloc_find_linux_cpuset_mntpnt(). /etc/fstab .. cpuset /dev/cpuset cpuset defaults 0 0 .. Brice Goglin wrote: > Le 22/07/2010 14:53, Michael Raymond a écrit : >> I was doing some testing on what's in SVN and I found that the >> topology discovery code has a problem when running within a cpuset. On >> my 2.6.32 SLES11SP1 box the code calls hwloc_read_linux_cpuset_mask() >> with a cgroup mount point and tries to read >> /dev/cpuset//cpuset.[cpus|mems]. Those files don't exist but >> /[cpus|mems] do. If I change the code to use those files instead >> then everything else works. >> > > Hello Michael, > This probably means that we found a cgroup mount point in /dev/cpuset > while its actually a cpuset mount point. What does your /proc/mounts > contain? Can you try to understand why hwloc_find_linux_cpuset_mntpnt > would find a wrong mount type? > thanks, > Brice -- Michael A. Raymond Message Passing Toolkit Team Silicon Graphics Inc (651) 683-3434
Re: [hwloc-devel] Cpuset problem
Le 22/07/2010 19:30, Michael Raymond a écrit : > /proc/mounts: > cpuset /dev/cpuset cgroup > rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0 > > The third element there is "cgroup" which the code specifically looks > for in hwloc_find_linux_cpuset_mntpnt(). > > /etc/fstab > .. > cpuset /dev/cpuset cpuset defaults >0 0 > .. > Ok, I see. Recent kernels directly mount "cpuset" as "cgroup" but they add the "noprefix" mount option to maintain backward compatibility with the old /dev/cpuset/ filenames. We need to either check whether noprefix is given in the mount options, or directly look for cpus/mems if cpuset.cpus/cpuset.mems do not exist. I'll fix this when after some testing. thanks, Brice
Re: [hwloc-devel] 1.0.2rc2 posted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 21/07/10 19:29, Samuel Thibault wrote: > To make distcheck from an svn export, you need to be able > to provide a complete distribution tarball, i.e. have tools > to build docs. You should rather use the released tarbal. I was using the 1.02rc2 tarball. - -- Christopher Samuel - Senior Systems Administrator VLSCI - Victorian Life Sciences Computational Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.unimelb.edu.au/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxI3aIACgkQO2KABBYQAh/jQgCeIYPxqBSicld8LNunOk+Fq0Ou rkAAoIDs0XMwat+6Eaq6LQeiONB6OBD4 =EbSK -END PGP SIGNATURE-
