DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 449] Fortville X710 FDIR with flow APIs broken
Date: Mon, 04 Jan 2021 03:15:29 +0000	[thread overview]
Message-ID: <bug-449-3-yLkDhcJZu6@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-449-3@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=449

Vipin Varghese (vipin.varghese@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |---
             Status|RESOLVED                    |CONFIRMED

--- Comment #14 from Vipin Varghese (vipin.varghese@intel.com) ---
Marking this as fixed `confirmed` rather than `resolved-invalid` due to the
following reasons

1. ticket is opened on DPDK 20.02 on 13 Apr 2020
2. The documentation available for FDIR on X710 was not correct
3. missing of `transfer` verb in the documentation of testpmd and tests.
4. Patches and fixes applied on top of X710 before testing on 30 Dec 2020.
5. Not mentioned in the comment whether it works for `DPDK 20.02`
6. Have not confirmed if the VF can be used with any other application other
than testpmd.

@Ajith will test and try on DPDK 20.02 but with much lower priority to confirm
with the steps shared from `Steve Yang` and update the ticket.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2021-01-04  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 11:42 bugzilla
2020-12-30  6:19 ` bugzilla
2021-01-04  3:15 ` bugzilla [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=bug-449-3-yLkDhcJZu6@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).