From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-fw-9102.amazon.com (smtp-fw-9102.amazon.com [207.171.184.29]) by dpdk.org (Postfix) with ESMTP id C89785906 for ; Wed, 18 Dec 2013 21:19:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1387398040; x=1418934040; h=from:to:subject:date:message-id:mime-version; bh=WdwsugoitfdN2tySGzY0PXbZlpPbczOHqAj7BPWWxGg=; b=FHLaJZpCqu+1tkkaQjWIoX73YVZNulC4dMxJKVTedILRhb/+RPOSYE2h qeBVkYmL9XLG0WUCb+znnoe9pUHkes525adIN5HU1QVO7FIPZXbiBBhsj 9V4urikZdoOSsVLu0XFyRzC6ctwKGuRgCN1K2Lhu8pt6eiA8FP3TpIo+j I=; X-IronPort-AV: E=Sophos;i="4.95,508,1384300800"; d="scan'208,217";a="47185320" Received: from smtp-in-1002.vdc.amazon.com ([10.118.132.23]) by smtp-border-fw-out-9102.sea19.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Dec 2013 20:20:26 +0000 Received: from ex10-hub-31002.ant.amazon.com (ex10-hub-31002.sea31.amazon.com [10.185.169.193]) by smtp-in-1002.vdc.amazon.com (8.14.7/8.14.7) with ESMTP id rBIKKNIK003840 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for ; Wed, 18 Dec 2013 20:20:24 GMT Received: from EX10-MBX-9002.ant.amazon.com ([fe80::f0a2:552e:430e:3cdb]) by ex10-hub-31002.ant.amazon.com ([::1]) with mapi id 14.02.0342.003; Wed, 18 Dec 2013 12:19:44 -0800 From: "Benson, Bryan" To: "dev@dpdk.org" Thread-Topic: PCI device mapping to socket Thread-Index: Ac78Ln0DRgJX6fkQQkeYdcs5ALqWow== Date: Wed, 18 Dec 2013 20:19:43 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.17.1.114] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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:19:33 -0000 All, Does anyone know of a way I can find out which socket a PCI device/bridge i= s tied up to? I have looked into dmidecode and lspci to no avail, but I ma= y be missing something. We are looking at putting multiple NICs into a sin= gle dual socket server. This is so that I can tie specific NIC ports to the proper socket to take a= dvantage of DDIO. Thank you, Bryan Benson Amazon Web Services