From: 曾懷恩 <the@csie.io>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: 張敬昊 <frank@csie.io>, users@dpdk.org
Subject: Re: [dpdk-users] Flow director struct rte_flow_item_raw guild
Date: Fri, 10 May 2019 14:38:56 +0800 [thread overview]
Message-ID: <BD5F2744-AA65-4C9E-BAD4-462C8F322FF6@csie.io> (raw)
In-Reply-To: <20190509123833.GF4284@6wind.com>
Hi Adrien, thanks for reply and explanation
I can understand the principle now.
However, I try to merge your rewriting code to mine and the ICMP packets seem not to fit this rule.
My ethernet card is Connectx-4 lx.
Can you give me some suggestion?
Thanks a lot.
Best Regards,
> Adrien Mazarguil <adrien.mazarguil@6wind.com> 於 2019年5月9日 下午8:38 寫道:
>
> rte_flow_item_raw_mask
next prev parent reply other threads:[~2019-05-10 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 2:01 曾懷恩
2019-05-09 2:10 ` 張敬昊
2019-05-09 3:51 ` 曾懷恩
2019-05-09 12:38 ` Adrien Mazarguil
2019-05-10 6:38 ` 曾懷恩 [this message]
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=BD5F2744-AA65-4C9E-BAD4-462C8F322FF6@csie.io \
--to=the@csie.io \
--cc=adrien.mazarguil@6wind.com \
--cc=frank@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).