[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-27 Thread bugproxy
** Tags removed: targetmilestone-inin16042 ** Tags added: targetmilestone-inin--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify n

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-22 Thread Nish Aravamudan
** Changed in: numactl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:de

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-15 Thread Nish Aravamudan
You're welcome! Note that there is an opportunity here (distro agnostic) for someone to write up an article explaining when numactl goes wrong (and why) in cases like this. I think they are seen more often on Power (due to LPARs). -- You received this bug notification because you are a member of

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-09 Thread Nish Aravamudan
I think the -1 means that we were unable to parse the OF representation of the NUMA node. I'd have to refresh my memory on the powerpc NUMA code, it might be faster to ask the Ozlabs folks. -Nish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-07 Thread Nish Aravamudan
Note that LPAR is so broken as far as affinity goes that I don't think any invocation of numactl on it makes sense. You have one node with all CPUs and one node with all memory. By definition, you will need to fallback to node 0 to run and to node 1 to allocate memory, so don't bother using numactl

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-07 Thread Nish Aravamudan
Ok, so I think this is not exactly a bug, maybe a usability issue upstream? Note also that the error message now reported ("Cannot read node mask for device", sysfs_node_read returning -1) is different than before ("Kernel does not know node mask for device", sysfs_node_read returning -2) In any

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-04 Thread Nish Aravamudan
Unfortunately numactl/libnuma is historically quite bad at making it easy to debug these kind of issues. Algorithmically, numactl does the following: If a /sys/class/net/ symlink is found and the target matches '/devices/pci[0-9a-fA-F:/]+\\.[0-9]+)/', it then tries to parse /sys//numa_node If th

[Bug 1638515] Re: Ubuntu 16.04.1: numactl failed when trying to specify node with netdev:dev

2016-11-02 Thread bugproxy
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16042 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638515 Title: Ubuntu 16.04.1: numactl failed when trying to specify n