DPDK patches and discussions
 help / color / mirror / Atom feed
From: hanoh haim <hhaim.hanoh@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Qos issue with new DPDK 20.02 and i40e driver
Date: Tue, 14 Jul 2020 16:08:42 +0300	[thread overview]
Message-ID: <CA+YxBo+=2Mr6Ctf5gFW=ri-jw_t=UwO942imewqeaD_XYHayhw@mail.gmail.com> (raw)

Hi i40e driver experts,
We are **not** a typical user of i40e dpdk driver, we are using tx Qos
configuration (dcb) with strict latency tx queues. The feature stops
working with a new firmware 7.0.x.
We are using DDP (another thing that is not standard) to solve the drop
rate issue.

dpdk 19.05 - works fine
dpdk 20.02 (with new firmware) - does not work

I tried to look into what changed between 19.05->20.02 that was related to
dbc and couldn't find. Our patch is rather small, for now we have a
workaround (allocating one more tx queue) but it has not solved the problem.

more info here:
https://github.com/cisco-system-traffic-generator/trex-core/issues/508

Does it ring a bell?

-- 
Hanoh
Sent from my iPhone

                 reply	other threads:[~2020-07-14 14:39 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='CA+YxBo+=2Mr6Ctf5gFW=ri-jw_t=UwO942imewqeaD_XYHayhw@mail.gmail.com' \
    --to=hhaim.hanoh@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).