patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Akhil Goyal <>
To: Konstantin Ananyev <>,
	Anoob Joseph <>,
	Radu Nicolau <>
Cc: Konstantin Ananyev <>,
	Jerin Jacob Kollanukkaran <>,
	"" <>,
	"" <>
Subject: RE: [PATCH 1/2] examples/ipsec-secgw: fix width of variables
Date: Tue, 9 Jan 2024 17:38:33 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> > 'rte_eth_rx_burst' returns uint16_t. The same value need to be passed
> > to 'process_packets' functions which performs further processing. Having
> > this function use 'uint8_t' can result in issues when MAX_PKT_BURST is
> > larger.
> >
> > The route functions (route4_pkts & route6_pkts) take uint8_t as the
> > argument. The caller can pass larger values as the field that is passed
> > is of type uint32_t. And the function can work with uint32_t as it loops
> > through the packets and sends it out. Using uint8_t can result in silent
> > packet drops.
> >
> > Fixes: 4fbfa6c7c921 ("examples/ipsec-secgw: update eth header during route
> lookup")


> >
> > Signed-off-by: Anoob Joseph <>
Acked-by: Akhil Goyal <>

Applied to dpdk-next-crypto
> Acked-by: Konstantin Ananyev <>
Email Id shows warning in mailmap
Contributor name/email mismatch with .mailmap:
        Konstantin Ananyev <> is not the primary email address

I believe Konstantin is using both email ids, but mailmap is taking the first one as primary one.
Is it possible for you to use a single email ID and update mailmap accordingly?

           reply	other threads:[~2024-01-09 17:38 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* 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).