From: Chas Williams <3chas3@gmail.com>
To: Alexander Belyakov <abelyako@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: bnx2x pmd performance expectations
Date: Sun, 27 Dec 2015 16:17:36 -0500 [thread overview]
Message-ID: <1451251056.1893.4.camel@gmail.com> (raw)
In-Reply-To: <CAAQJX_RxD_ifaw8e5H3bw6k6GxmPLhOsiFiTneMFer7LrsHv9g@mail.gmail.com>
I wouldn't consider myself an expert on this driver but while looking
at some other things, I have noted that RTE_PMD_BNX2X_TX_MAX_BURST is
defined to be 1. This bursts single packets to bnx2x_tx_encap() but it
looks like bnx2x_tx_encap() is far more capable than that.
On Tue, 2015-12-22 at 14:52 +0300, Alexander Belyakov wrote:
> Hi,
>
> just tried to forward a lot of tiny packets with testpmd (dpdk-2.2.0)
> running on Broadcom Corporation NetXtreme II BCM57810S 10 Gigabit
> Ethernet
> (rev 10) adapter. I see forwarding performance of 2.6Mpps instead of
> expected 14.8Mpps. What should be done to achieve better results?
>
> Thank you,
> Alexander Belyakov
next prev parent reply other threads:[~2015-12-27 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 11:52 bnx2x pmd performance expectations Alexander Belyakov
2015-12-27 21:17 ` Chas Williams [this message]
2015-12-29 8:15 ` Alexander Belyakov
2015-12-29 17:24 ` Harish Patil
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=1451251056.1893.4.camel@gmail.com \
--to=3chas3@gmail.com \
--cc=abelyako@gmail.com \
--cc=dev@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).