From: Stephen Hemminger <stephen@networkplumber.org>
To: "Đỗ Hoàng" <mon120494@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Performance issue with 82546EB NICs
Date: Fri, 19 Aug 2016 11:06:07 -0700 [thread overview]
Message-ID: <20160819110607.0d958994@xeon-e3> (raw)
In-Reply-To: <CAHzS=K9yU2e_EZAR3ZyH0XvP0LpQBua=qDYBZSm=j3Hy8LA-SQ@mail.gmail.com>
On Fri, 19 Aug 2016 08:53:12 +0800
Đỗ Hoàng <mon120494@gmail.com> wrote:
> Hi all,
>
> I am using a dual-port Intel 82546EB to run the simple l2fwd application
> (forward 64byte packets).
>
> The result is terrible. My packet generator generates and sends about
> 320Mb/s, but nearly a half of them are dropped, and only about 160Mb of
> packets are forwarded every sec.
>
> I have also tried to run dpdk-pktgen with this NIC and It can only generate
> and send about 150Mb/s.
>
> My NIC link speed is 1000Mb/s. I am wondering why its performance is so
> slow like this.
>
> Please help me. Any ideas/advices are appreciated.
>
> Thanks.
The first thing I would check is that ethernet flow control is disabled.
Unless you are running on very slow hardware, the DPDK can saturate a 10G
link with small packets.
prev parent reply other threads:[~2016-08-19 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 0:53 Đỗ Hoàng
2016-08-19 18:06 ` 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=20160819110607.0d958994@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=mon120494@gmail.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).