DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 526] ixgbe: X550 flow type ETH / VLAN / RAW not supported
Date: Fri, 14 Aug 2020 10:06:59 +0000	[thread overview]
Message-ID: <bug-526-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 526
           Summary: ixgbe: X550 flow type ETH / VLAN / RAW not supported
           Product: DPDK
           Version: 20.05
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: pawelwod@gmail.com
  Target Milestone: ---

While trying to add ETH / VLAN it works OK. But when trying ETH / VLAN / RAW
with RAW item & mask:

        struct rte_flow_item_raw raw = {};
        raw.relative = 0;
        raw.search = 0;
        raw.reserved = 0;
        raw.offset = off;
        raw.limit = 0;
        raw.length = 2;

        raw.pattern = (uint8_t *)&raw_pattern;

        struct rte_flow_item_raw raw_mask = {};
        raw_mask.relative = 1;
        raw_mask.search = 1;
        raw_mask.reserved = 0;
        raw_mask.offset = 0xffffffff;
        raw_mask.limit = 0xffff;
        raw_mask.length = 0xffff;

        uint16_t raw_mask_pattern = 0xffff;
        raw_mask.pattern = (uint8_t *)&raw_mask_pattern;

        item->type = RTE_FLOW_ITEM_TYPE_RAW;
        item->spec = (void *)&raw;
        item->mask = (void *)&raw_mask;

It returns: EINVAL: "Not supported by fdir filter"

This NIC (and others from ixgbe) support FLEX bytes so it should be considered
as a bug.

I can't test DPDK version > 20.05 but since fdir code is quite the same I think
it is presen in master branch as well.

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

                 reply	other threads:[~2020-08-14 10:07 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=bug-526-3@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).