From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from HUB024-nj-3.exch024.serverdata.net (hub024-nj-3.exch024.serverdata.net [206.225.165.118]) by dpdk.org (Postfix) with ESMTP id D457E68DD for ; Mon, 3 Mar 2014 01:54:59 +0100 (CET) Received: from MBX024-E1-NJ-4.exch024.domain.local ([10.240.10.54]) by HUB024-NJ-3.exch024.domain.local ([10.240.10.36]) with mapi id 14.03.0174.001; Sun, 2 Mar 2014 16:56:27 -0800 From: Jane Shen To: "dev@dpdk.org" Thread-Topic: Physical core vs. hyper threaded core Thread-Index: Ac82Vrk+hXP+o9JVR2ubvxJCfNUDfA== Date: Mon, 3 Mar 2014 00:56:26 +0000 Message-ID: <96144595DCDF66419CB40342CCD31E2E3E441B43@mbx024-e1-nj-4.exch024.domain.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [38.122.186.90] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Physical core vs. hyper threaded core 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: Mon, 03 Mar 2014 00:55:00 -0000 Hi, I understand that DPDK should use the physical core. But here is what we te= sted: - Enable HT - Assign 8 cores of the CPU (an 8-core Sandybridge CPU) to DPDK. Surprisingly enough, we noticed that the remaining 8 cores (b/c there are t= otal of 16 cores after HT) can still handle other Linux processes which are= SIP based signaling transactions. Anybody can shed some light on how this worked? Is there anybody tried simi= lar thing? What has been your experience? Thanks, -Jane