From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Nicolau, Radu" <radu.nicolau@intel.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Buckley, Daniel M" <daniel.m.buckley@intel.com>
Subject: RE: [PATCH] examples/ipsec-secgw: fix packet type parsing
Date: Tue, 14 Jun 2022 15:47:58 +0000 [thread overview]
Message-ID: <MW5PR11MB5809BE0B04FFEC5D7577DF5AB8AA9@MW5PR11MB5809.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220610104554.1395317-1-radu.nicolau@intel.com>
> -----Original Message-----
> From: Radu Nicolau <radu.nicolau@intel.com>
> Sent: Friday, June 10, 2022 11:46 AM
> To: Nicolau, Radu <radu.nicolau@intel.com>; Akhil Goyal <gakhil@marvell.com>
> Cc: dev@dpdk.org; Buckley, Daniel M <daniel.m.buckley@intel.com>
> Subject: [PATCH] examples/ipsec-secgw: fix packet type parsing
>
> Add new packet type flags instead of overwriting.
>
> Fixes: d04bb1c52647 ("examples/ipsec-secgw: use HW parsed packet type in
> poll mode")
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> ---
> examples/ipsec-secgw/ipsec-secgw.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/examples/ipsec-secgw/ipsec-secgw.c b/examples/ipsec-secgw/ipsec-
> secgw.c
> index 25255e053c..2391be8081 100644
> --- a/examples/ipsec-secgw/ipsec-secgw.c
> +++ b/examples/ipsec-secgw/ipsec-secgw.c
> @@ -1795,7 +1795,7 @@ parse_ptype(struct rte_mbuf *m)
> break;
> }
> exit:
> - m->packet_type = packet_type;
> + m->packet_type |= packet_type;
> }
>
> static uint16_t
> --
> 2.25.1
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2022-06-14 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 10:45 Radu Nicolau
2022-06-14 15:47 ` Zhang, Roy Fan [this message]
2022-06-15 15:17 ` Akhil Goyal
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=MW5PR11MB5809BE0B04FFEC5D7577DF5AB8AA9@MW5PR11MB5809.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=daniel.m.buckley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=radu.nicolau@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).