DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jane Shen <jshen@mavenir.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Physical core vs. hyper threaded core
Date: Mon, 3 Mar 2014 00:56:26 +0000	[thread overview]
Message-ID: <96144595DCDF66419CB40342CCD31E2E3E441B43@mbx024-e1-nj-4.exch024.domain.local> (raw)

Hi,

I understand that DPDK should use the physical core. But here is what we tested:

-          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 total 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 similar thing? What has been your experience?

Thanks,
-Jane

             reply	other threads:[~2014-03-03  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03  0:56 Jane Shen [this message]
2014-03-03  1:49 ` Jayakumar, Muthurajan
2014-03-03  2:14   ` Jane Shen
2014-03-03  2:22     ` Jayakumar, Muthurajan
2014-03-03  2:54       ` Jayakumar, Muthurajan
2014-03-03 19:49         ` Jane Shen
2014-03-03 20:11           ` Jayakumar, Muthurajan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=96144595DCDF66419CB40342CCD31E2E3E441B43@mbx024-e1-nj-4.exch024.domain.local \
    --to=jshen@mavenir.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).