From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Jie1X" <jie1x.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, SteveX" <stevex.yang@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Subject: RE: [PATCH] net/iavf: support raw packet for flow subscription
Date: Thu, 13 Oct 2022 06:03:38 +0000 [thread overview]
Message-ID: <DM4PR11MB599418F3A74E1478964FFFA7D7259@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221009090037.78015-1-jie1x.wang@intel.com>
> -----Original Message-----
> From: Wang, Jie1X <jie1x.wang@intel.com>
> Sent: Sunday, October 9, 2022 5:01 PM
> To: dev@dpdk.org
> Cc: Yang, SteveX <stevex.yang@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>; Yang, Qiming <qiming.yang@intel.com>; Wu,
> Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>; Wang,
> Jie1X <jie1x.wang@intel.com>
> Subject: [PATCH] net/iavf: support raw packet for flow subscription
>
> Add Protocol Agnostic Flow (raw flow) support for flow subscription in AVF.
>
> For example, testpmd creates a flow subscription raw packet rule:
> rule: eth + ipv4 src is 1.1.1.1 dst is 2.2.2.2
>
> cmd: flow create 0 ingress pattern raw pattern spec \
> 0000000000000000000000000800450000140000000000000000010101010202
> 0202 \ pattern mask \
> 0000000000000000000000000000000000000000000000000000FFFFFFFFFFFFFF
> FF \ / end actions port_representor port_id 0 / passthru / end
>
> Signed-off-by: Jie Wang <jie1x.wang@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
prev parent reply other threads:[~2022-10-13 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 9:00 Jie Wang
2022-10-13 6:03 ` Zhang, Qi Z [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=DM4PR11MB599418F3A74E1478964FFFA7D7259@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jie1x.wang@intel.com \
--cc=jingjing.wu@intel.com \
--cc=qiming.yang@intel.com \
--cc=stevex.yang@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).