From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mo4.mail-out.ovh.net (4.mo4.mail-out.ovh.net [178.32.98.131]) by dpdk.org (Postfix) with ESMTP id 1143C5906 for ; Wed, 18 Dec 2013 21:43:46 +0100 (CET) Received: from mail173.ha.ovh.net (gw6.ovh.net [213.251.189.206]) by mo4.mail-out.ovh.net (Postfix) with SMTP id 2FBD1FFA4A7 for ; Wed, 18 Dec 2013 21:47:59 +0100 (CET) Received: from b0.ovh.net (HELO queueout) (213.186.33.50) by b0.ovh.net with SMTP; 18 Dec 2013 23:06:05 +0200 Received: from lneuilly-152-23-9-75.w193-252.abo.wanadoo.fr (HELO pcdeff) (ff@ozog.com@193.252.40.75) by ns0.ovh.net with SMTP; 18 Dec 2013 23:06:04 +0200 From: =?iso-8859-1?Q?Fran=E7ois-Fr=E9d=E9ric_Ozog?= To: "'Benson, Bryan'" , References: In-Reply-To: Date: Wed, 18 Dec 2013 21:42:58 +0100 Message-ID: <02e901cefc31$bcfda6a0$36f8f3e0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac78Ln0DRgJX6fkQQkeYdcs5ALqWowAAZoLA Content-Language: fr X-Ovh-Tracer-Id: 1025694816483989736 X-Ovh-Remote: 193.252.40.75 (lneuilly-152-23-9-75.w193-252.abo.wanadoo.fr) X-Ovh-Local: 213.186.33.20 (ns0.ovh.net) X-OVH-SPAMSTATE: OK X-OVH-SPAMSCORE: -100 X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeejtddrtddvucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd X-Spam-Check: DONE|U 0.5/N X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeejtddrtddvucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd Subject: Re: [dpdk-dev] PCI device mapping to socket X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 20:43:46 -0000 Hi, It depends on the kernel version. For the latests ones you can use: cat /sys/class/net//device/numa_node in all other case, you can use lspci fallback (in case even no driver is = yet loaded). lspci | grep Ethernet 09:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 09:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) lspci -t \-[0000:00]-+-00.0 +-01.0-[01-03]----00.0-[02-03]----08.0-[03]--+-00.0 | +-00.3 . . +-1c.0-[09-0a]--+-00.0 | +-00.1 | +-00.2 | \-00.3 So the PCI bus is 0. Now transform this to socket number: Space=3D0x100/ On a dual socket space=3D0x80, bus(0*space=3D0) is socket 0, = bus(1*space=3D0x80) is socket1. On a quad socket space=3D0x40, bus(0*space=3D0) is socket 0, = bus(1*space=3D0x40) is socket1, bus(2*space=3D0x80) is socket2, bus(3*space=3D0xc0) is = socket3 . Fran=E7ois-Fr=E9d=E9ric > -----Message d'origine----- > De=A0: dev [mailto:dev-bounces@dpdk.org] De la part de Benson, Bryan > Envoy=E9=A0: mercredi 18 d=E9cembre 2013 21:20 > =C0=A0: dev@dpdk.org > Objet=A0: [dpdk-dev] PCI device mapping to socket >=20 > All, > Does anyone know of a way I can find out which socket a PCI = device/bridge > is tied up to? I have looked into dmidecode and lspci to no avail, = but I > may be missing something. We are looking at putting multiple NICs = into a > single dual socket server. >=20 > This is so that I can tie specific NIC ports to the proper socket to = take > advantage of DDIO. >=20 > Thank you, > Bryan Benson > Amazon Web Services