DPDK usage discussions
 help / color / mirror / Atom feed
From: Antoine POLLENUS <a.pollenus@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Issues with rte_flow_destroy
Date: Wed, 26 May 2021 07:10:23 +0000	[thread overview]
Message-ID: <0f358466baa147f79e7d6c983df630ba@deltacast.tv> (raw)

I've also test using directly the flow director capabilities using ethtool and there it seems there is no issues I can make the same work flow as I want.

I've also test through DPDK with a XL710 (40G) and I have the same issues it seems the issue come from someware in the i40e functions. Maybe the validate.

This is really blocking for us and I have no idea how to fix that or any work around.

thank you in advance for your help,

regards

Antoine Pollenus

             reply	other threads:[~2021-05-26  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  7:10 Antoine POLLENUS [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-01 11:54 Antoine POLLENUS
2021-05-28  9:23 Antoine POLLENUS
2021-05-25 12:34 Antoine POLLENUS
2021-05-27  8:27 ` Xing, Beilei

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=0f358466baa147f79e7d6c983df630ba@deltacast.tv \
    --to=a.pollenus@deltacast.tv \
    --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).