DPDK usage discussions
 help / color / mirror / Atom feed
From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Zhiyong Huo <zhuo@SonicWall.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] dpdk sw schedule issue
Date: Fri, 31 Jul 2020 08:56:23 +0000
Message-ID: <BL0PR11MB313710DD567F9FD3B4D0AD69D74E0@BL0PR11MB3137.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MWHPR1801MB2061B9C4B065C5779FFA3449D3710@MWHPR1801MB2061.namprd18.prod.outlook.com>

> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Zhiyong Huo
> Sent: Thursday, July 30, 2020 4:05 AM
> To: users@dpdk.org
> Subject: [dpdk-users] dpdk sw schedule issue
> Hi,

Hi Huo,

> 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.

Would you describe your pipeline? Aka, what Eventdev Queues do you configure? (How many, and Atomic or Ordered?)

> 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.

You mention not using a service core, does this mean that the scheduler is being run
on a thread that is also doing other work? Best performance is often achieved by giving
a dedicated thread for the scheduling work in event_sw.

> 2.  Set multi RX polling adapeters and multi schedulers.
> Get higher performance but not as expect.

The results are not as you expect - do you mean that the packet tx order is not identical to rx?
That would be an expected side-effect of using e.g. RSS to spread work to e.g. 4 NIC rx queues.

Please describe what you are trying to achieve, and what was not as expected in more detail.

> For the scheduler logic, it seemed that the DPDK has very simple scheduler logic.
> Is there any plan or suggestion about the scheduler logic?

The PMD is documented in the DPDK docs here:

The scheduling logic is based around Atomic and Ordered packet scheduling logic. I'm
not sure what you mean by very simple scheduler logic.

> Thanks

Regards, -Harry

      reply	other threads:[~2020-07-31  8:56 UTC|newest]

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

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:

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

  git send-email \
    --in-reply-to=BL0PR11MB313710DD567F9FD3B4D0AD69D74E0@BL0PR11MB3137.namprd11.prod.outlook.com \
    --to=harry.van.haaren@intel.com \
    --cc=users@dpdk.org \
    --cc=zhuo@SonicWall.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git