DPDK usage discussions
 help / color / mirror / Atom feed
From: Zhiyong Huo <zhuo@SonicWall.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] dpdk sw schedule issue
Date: Thu, 30 Jul 2020 03:05:05 +0000	[thread overview]
Message-ID: <MWHPR1801MB2061B9C4B065C5779FFA3449D3710@MWHPR1801MB2061.namprd18.prod.outlook.com> (raw)

Hi,

We used DPDK to do high performance gateway.
And we chose the event_sw scheduler to do the packet scheduler.
However, there were several issues.

The gateway was set with 32 cores.
I did several test:


1.  One RX polling adapter and  one scheduler. No service core, but 32 cores to  compete the RX adapeter/scheduler adapter.

The performance was too low.



2.  Set multi RX polling adapeters and multi schedulers.

Get higher performance but not as expect.


For the scheduler logic, it seemed that the DPDK has very simple scheduler logic.

Is there any plan or suggestion about the scheduler logic?


Thanks


             reply	other threads:[~2020-07-30 23:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  3:05 Zhiyong Huo [this message]
2020-07-31  8:56 ` Van Haaren, Harry

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=MWHPR1801MB2061B9C4B065C5779FFA3449D3710@MWHPR1801MB2061.namprd18.prod.outlook.com \
    --to=zhuo@sonicwall.com \
    --cc=users@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).