From: Hugo Menna Barreto <hugombarreto@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Significant performance penalty when using flow director in Intel 82599ES
Date: Mon, 29 Jan 2018 15:29:57 -0200 [thread overview]
Message-ID: <CAAbAiaaBw4DfAGMKnPETNu6FOxFYmoOHm40oFPVSyX9HLVZ2Sg@mail.gmail.com> (raw)
Hi,
I am using an Intel 82599ES NIC with DPDK. Without activating flow director
I am able to process 64B packets at line rate (10Gbps). Unfortunately, as
soon as I activate flow director, the maximum throughput is around 5Gbps --
above this rate the NIC starts dropping packets.
Trying to isolate the problem I inspected the struct obtained using
"rte_eth_stats_get". Interestingly "rte_eth_stats.imissed" is going up
while "rte_eth_stats.rx_nombuf" remains at zero. As far as I know "imissed"
is linked to the MPC register and, therefore, indicates that the NIC buffer
is full.
I can imagine that activating flow director may impact performance -- as it
reduces the effective rx packet buffer size from 512KB to 448KB. However, I
did not expect the impact to be of such proportions. Therefore I am
suspicious that I may be doing something wrong.
My questions are:
When using flow director, is only getting half the throughput the expected
behavior? If it is, is there any direction one should follow in order to --
at least partially -- mitigate this problem? (e.g., would RSC help in this
case?) If it isn't, any ideas so far on what I may be doing wrong?
Thank you for your attention.
Best regards,
Hugo
p.s.
Some relevant fields of "rte_eth_conf":
-------------------------------------
rte_eth_conf {
[...]
.rxmode = {
.mq_mode = ETH_MQ_RX_NONE
[...]
}
.fdir_conf = {
.mode = RTE_FDIR_MODE_SIGNATURE,
.pballoc = RTE_FDIR_PBALLOC_64K,
.status = RTE_FDIR_REPORT_STATUS_ALWAYS,
[...]
}
}
Some extra details:
-------------------
* DPDK version: 17.08.1
* NIC: Intel 82599ES (ixgbe)
* CPU: E5-2650 (Sandy Bridge)
* PCIe: Gen2, Speed 5GT/s, Width x8
reply other threads:[~2018-01-29 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAAbAiaaBw4DfAGMKnPETNu6FOxFYmoOHm40oFPVSyX9HLVZ2Sg@mail.gmail.com \
--to=hugombarreto@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).