From: Thomas Monjalon <thomas@monjalon.net>
To: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Cc: dev@dpdk.org, 胡嘉瑜 <hujiayu.hu@foxmail.com>, stable@dpdk.org
Subject: Re: [PATCH v13] gro: fix reordering of packets in GRO layer
Date: Mon, 12 Feb 2024 15:30:19 +0100 [thread overview]
Message-ID: <11463992.MucGe3eQFb@thomas> (raw)
In-Reply-To: <tencent_5179002D180D87F2372968176C1FEEF04307@qq.com>
16/01/2024 15:28, 胡嘉瑜:
>
> 在 2024/1/9 上午12:04, Kumara Parameshwaran 写道:
> > In the current implementation when a packet is received with
> > special TCP flag(s) set, only that packet is delivered out of order.
> > There could be already coalesced packets in the GRO table
> > belonging to the same flow but not delivered.
> > This fix makes sure that the entire segment is delivered with the
> > special flag(s) set which is how the Linux GRO is also implemented
> >
> > Signed-off-by: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
>
> Reviewed-by: Jiayu Hu <hujiayu.hu@foxmail.com>
Applied with Cc stable, thanks.
parent reply other threads:[~2024-02-12 14:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_5179002D180D87F2372968176C1FEEF04307@qq.com>]
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=11463992.MucGe3eQFb@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hujiayu.hu@foxmail.com \
--cc=kumaraparamesh92@gmail.com \
--cc=stable@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).