DPDK usage discussions
 help / color / mirror / Atom feed
From: Staffan Wiklund <staffan491@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users <users@dpdk.org>
Subject: Re: Are Intel CPUs better than AMD CPUs for DPDK applications?
Date: Tue, 22 Feb 2022 20:35:13 +0100	[thread overview]
Message-ID: <CAAV4wTi2dpzhOCqN4Um5sbva-Z7=mTT0wG6D+JGptW7omyWqiA@mail.gmail.com> (raw)
In-Reply-To: <20220221174902.115c1eed@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]

Thanks Stephen again for your help.
I will check out what you mentioned about CPU features.

By the way, regarding my earlier question about using DPDK memif in a
Docker container.
I made a patch in the memif driver of DPDK so it uses a TCP socket instead
of a UNIX domain socket.
This made it possible to communicate between a Docker container and an
application outside the container using DPDK memif.
This patch only works without the "zero-copy" option for DPDK memif.
But the throughput of DPDK memif without zero-copy is rather good anyway.

Regards
Staffan


Den tis 22 feb. 2022 kl 02:49 skrev Stephen Hemminger <
stephen@networkplumber.org>:

> On Mon, 21 Feb 2022 21:28:08 +0100
> Staffan Wiklund <staffan491@gmail.com> wrote:
>
> > Stephen, thanks for your answer.
> > I realize the statement is very vague.
> > I was thinking of if there was something common in the design of Intel
> and
> > AMD CPUs respectively that has an impact on their use by DPDK
> applications.
> > Do you know if there is such a common design difference between Intel and
> > AMD CPUs or is it just a matter of using an Intel or AMD CPU with the
> > requested performance?
> >
> > Regards
> > Staffan
>
> I am not a CPU expert. But compare memory bandwidth, clock rate, PCI
> Express version
> and support for AVX support (for some features). There a few places in DPDK
> that can use AVX512 but it is limited
> https://doc.dpdk.org/guides/howto/avx512.html
>
> Also there is a tradeoff with more cores, NUMA, etc as well as cost.
>
> Don't believe simple tribal knowledge, you need to look under the covers.
>

[-- Attachment #2: Type: text/html, Size: 2271 bytes --]

      reply	other threads:[~2022-02-22 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 15:14 Staffan Wiklund
2022-02-21 17:08 ` Stephen Hemminger
2022-02-21 20:28   ` Staffan Wiklund
2022-02-22  1:49     ` Stephen Hemminger
2022-02-22 19:35       ` Staffan Wiklund [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:
  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='CAAV4wTi2dpzhOCqN4Um5sbva-Z7=mTT0wG6D+JGptW7omyWqiA@mail.gmail.com' \
    --to=staffan491@gmail.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
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).