From: 張敬昊 <frank@csie.io>
To: 曾懷恩 <the@csie.io>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Flow director struct rte_flow_item_raw guild
Date: Thu, 9 May 2019 10:10:32 +0800 [thread overview]
Message-ID: <CA+vFTf-OYYs4XdShx1uy0NHCQHv9r-E=xERQsUte4piV1zOvRQ@mail.gmail.com> (raw)
In-Reply-To: <B09B9695-26BC-420C-B54C-BB858E08099F@csie.io>
Hi 懷恩,
On the second line of the detailed description of the struct reference
<https://doc.dpdk.org/api/structrte__flow__item__raw.html#a0ea66fcaa4ad84410cef13b693809bd2>,
it says
"Matches a byte string of a given length at a given offset."
I think *pattern* is the byte string to look for.
Regards,
Frank
On Thu, May 9, 2019 at 10:01 AM 曾懷恩 <the@csie.io> wrote:
>
> Hi,
>
> I have a few questions about structure rte_flow_item_raw.
>
> In DPDK API doc, it shows there are some below elements in this structure
>
> uint32_t relative:1
> uint32_t search:1
> uint32_t reserved:30
> int32_t offset
> uint16_t limit
> uint16_t length
> const uint8_t * pattern
>
> Now I can understand the relative and search elements are used to
> determine search type.
>
> The offset element is used to set the start search point in packet.
>
> The limit element is used to set the end search point in packet.
>
> However, I can’t understand what the pattern element is used to?
>
> What kind of pointer should I assign to the pattern element?
>
> Besides, in other rte_flow_item_* structures, there are clearly elements
> to let user to set contents and masks.
>
> How do I do in the structure rte_flow_item_raw?
>
> Thanks a lot,
>
> Best Regards,
>
>
--
張敬昊 Frank Chang
Email: frank@csie.io
https://frankchang.me
*High Speed Network Lab <http://speed.cis.nctu.edu.tw/>*
*National Chiao Tung University*
next prev parent reply other threads:[~2019-05-09 2:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 2:01 曾懷恩
2019-05-09 2:10 ` 張敬昊 [this message]
2019-05-09 3:51 ` 曾懷恩
2019-05-09 12:38 ` Adrien Mazarguil
2019-05-10 6:38 ` 曾懷恩
2019-05-10 13:44 ` Adrien Mazarguil
2019-05-10 18:20 ` Huai-En Tseng
2019-05-13 8:49 ` Adrien Mazarguil
2019-05-16 5:34 ` 曾懷恩
2019-05-16 6:00 ` Tom Barbette
2019-05-22 3:18 ` 曾懷恩
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+vFTf-OYYs4XdShx1uy0NHCQHv9r-E=xERQsUte4piV1zOvRQ@mail.gmail.com' \
--to=frank@csie.io \
--cc=the@csie.io \
--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).