DPDK usage discussions
 help / color / mirror / Atom feed
From: Jared Brown <cpu-dpdk@mail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] DPDK CPU selection criteria?
Date: Fri, 17 Sep 2021 18:22:11 +0200
Message-ID: <trinity-6b1ab2b1-ed1a-4362-99ae-cd20f8389b5e-1631895731768@3c-app-mailcom-lxa11> (raw)
In-Reply-To: <20210917085158.407f7bd4@hermes.local>

> Intentionally, in fact any reference to any one CPU vendor should be removed from website and documentaton.
  I get where this is coming from, but all the same it is not very useful to the end user, given that the title of the document is "7. How to get best performance with NICs on Intel platforms". One would expect some accurate and actionable advice on how to get the best performance.


> Also any performance is application dependent. If you have an application that
> is very well tuned then some of this matters, for other applications which have
> other issues (syscalls, locks, huge cache footprint) none of this matters.
  Obviously performance is application dependent, but all things being equal one would with good reason expect the underlying hardware to affect the performance. If it does not, why are magnitudes of difference being reported on per core Mpps performance?

  What I am trying to find out is, which factors *do* matter.

  Is there really no data or experience based knowledge about hardware forwarding performance out there, or is everybody supposed to find out things by trial and error?


- Jared

  reply	other threads:[~2021-09-17 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 15:23 Jared Brown
2021-09-17 15:51 ` Stephen Hemminger
2021-09-17 16:22   ` Jared Brown [this message]
2021-09-29 10:30 ` Thomas Monjalon
2021-09-30  9:26   ` Kinsella, Ray

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=trinity-6b1ab2b1-ed1a-4362-99ae-cd20f8389b5e-1631895731768@3c-app-mailcom-lxa11 \
    --to=cpu-dpdk@mail.com \
    --cc=stephen@networkplumber.org \
    --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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://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/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


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