DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>
Cc: "Peng, Yuan" <yuan.peng@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: Re: [dpdk-dev] raw pattern for rte_flow
Date: Mon, 17 Dec 2018 07:17:59 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07E8BD81@PGSMSX103.gar.corp.intel.com> (raw)

More info for this problem:
Old type filter can get actual number from CLI because there is a function xdigit2val(unsigned char c)  for it.
Maybe flow CLI also need one.

From: Zhao1, Wei
Sent: Monday, December 17, 2018 3:06 PM
To: adrien.mazarguil@6wind.com
Cc: Peng, Yuan <yuan.peng@intel.com>; dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>
Subject: raw pattern for rte_flow

Hi,adrien
By now, we need to enable flexible byte filter for ixgbe, but PMD can not work well.
Because in RTE_FLOW_ITEM_TYPE_RAW type pattern, the key parameters (const uint8_t *pattern)  in struct rte_flow_item_raw,
which we get rte_flow command line is ASIC number not the actual number.
For example, if we  type in the following command, PMD will get “0x6463” for “cd” not “11011100”, this make filter hard to search some specific parameters.
AND also, it is realted to all type of NIC, not only IXGBE .


Flow create 0 ingress pattern raw relative spec 0 relative mask 1 search spec 0 search mask 1 offset spec 54 offset mask 0xffffffff limit spec 0 limit mask 0xffff pattern is cd / end actions queue index 2 / end

struct rte_flow_item_raw {
                uint32_t relative:1; /**< Look for pattern after the previous item. */
                uint32_t search:1; /**< Search pattern from offset (see also limit). */
                uint32_t reserved:30; /**< Reserved, must be set to zero. */
                int32_t offset; /**< Absolute or relative offset for pattern. */
                uint16_t limit; /**< Search area limit for start of pattern. */
                uint16_t length; /**< Pattern length. */
                const uint8_t *pattern; /**< Byte string to look for. */
};

             reply	other threads:[~2018-12-17  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17  7:17 Zhao1, Wei [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-17  7:05 Zhao1, Wei

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=A2573D2ACFCADC41BB3BE09C6DE313CA07E8BD81@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=yuan.peng@intel.com \
    /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).