From: Stephen Hemminger <stephen@networkplumber.org>
To: "Geen Tseng 曾昱杰" <Geen.Tseng@wpi-group.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"Chester Chen 陳志霖" <chester.chen@wpi-group.com>
Subject: Re: [dpdk-users] DPDK question
Date: Tue, 30 Jul 2019 08:27:52 -0700 [thread overview]
Message-ID: <20190730082752.455e9ae3@hermes.lan> (raw)
In-Reply-To: <3D275741E88B5C4A96D0FE5CBE7FEF9B0A2DA654@TWEX03.wpgholdings.com>
On Mon, 29 Jul 2019 07:52:29 +0000
Geen Tseng 曾昱杰 <Geen.Tseng@wpi-group.com> wrote:
> Hi Sir
>
> One question.
>
> Is there a chance to achieve DPDK performance
>
>
> if we use NIC not in DPDK support driver list
>
> Thanks
>
> World Peace Industrial Co., Ltd.
> Geen Tseng
> Office: 2788-5200 #86571
> Email : geen.tseng@wpi-group.com
Most ways of interacting with network without driver support are
slower than native kernel networking. AF_XDP has promise of being
faster but it still uses more CPU than native DPDK driver.
prev parent reply other threads:[~2019-07-30 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 7:52 Geen Tseng 曾昱杰
2019-07-30 15:27 ` Stephen Hemminger [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=20190730082752.455e9ae3@hermes.lan \
--to=stephen@networkplumber.org \
--cc=Geen.Tseng@wpi-group.com \
--cc=chester.chen@wpi-group.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).