lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1663671447309288@web21m.yandex.ru>
Date:	Thu, 12 Nov 2015 09:21:28 +0300
From:	Oleg A Arkhangelsky <sysoleg@...dex.ru>
To:	Vincent Li <vincent.mc.li@...il.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Why my NIC shows NUMA -1?



12.11.2015, 01:41, "Vincent Li" <vincent.mc.li@...il.com>:
> Hi
>
> Sorry I am not sure if this is the right list to ask this question,
> please direct me to the correct one. thanks!
>
> I am using Intel 82599 on Dell PowerEdge R710 which should support
> NUMA node, the box is running ubuntu 14.01.1 LTS , I am wondering why I
> get NUMA socket -1.
>
> in BIOS, the memory "Node Interleaving" is
> disabled by default and I am using DPDK and DPDK sees my NIC NUMA -1,
> but i guess it is
> not related to DPDK since the sysfs shows NUMA -1, any clue?

numa_node value is set according to information provided by BIOS _PXM
table.

This can be related to your question:
https://patchwork.ozlabs.org/patch/400073/

--
wbr, Oleg.

"Anarchy is about taking complete responsibility for yourself."
      Alan Moore.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ