DPDK patches and discussions
 help / color / mirror / Atom feed
From: 张伟 <zhangwqh@126.com>
To: dev@dpdk.org
Subject: [dpdk-dev] two different threads polls the same port, different queues, why the throughput is the same
Date: Mon, 14 Nov 2016 13:28:33 +0800 (CST)	[thread overview]
Message-ID: <6a6fff02.604d.158614ef009.Coremail.zhangwqh@126.com> (raw)

Hi all, 


I have two threads process the packets with different ways. thread A (core 0) is very heavy, thread B (core 1) is very light.   If I just run each of them, their throughput is huge different with small packet. Thread A polls queue 0 of port 0, thread B polls queue 1 of port 0. If I run them at the same time, why thread A and thread B get same throughput. This makes me very confused. Does anyone have the same experience or know some possible reasons?  


Thanks, 
wei

             reply	other threads:[~2016-11-14  5:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  5:28 张伟 [this message]
     [not found] ` <CAMFWN9=sA9v3-PwC_WnSdRYSNnR=Pe-k9PeMib2enwr-9bPh5A@mail.gmail.com>
2016-11-14  6:34   ` 张伟

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=6a6fff02.604d.158614ef009.Coremail.zhangwqh@126.com \
    --to=zhangwqh@126.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).