From: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
To: hujiayu.hu@foxmail.com
Cc: dev@dpdk.org
Subject: Re: [PATCH v1] gro : packets not getting flushed in heavy-weight mode API
Date: Thu, 18 Jan 2024 01:27:57 +0530 [thread overview]
Message-ID: <CANxNyaszTnDf4kLBC2xgVtyrtu3aCm8G=nH19ZRUzwerqkx1EQ@mail.gmail.com> (raw)
In-Reply-To: <20240117195228.423261-1-kumaraparamesh92@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
On Thu, Jan 18, 2024 at 1:22 AM Kumara Parameshwaran <
kumaraparamesh92@gmail.com> wrote:
> In heavy-weight mode GRO which is based on timer, the GRO packets will not
> be
> flushed inspite of timer expiry if there is no packet in the current poll.
> If timer mode GRO is enabled the rte_gro_timeout_flush API should be
> invoked.
>
> Signed-off-by: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
> ---
> v1:
> Changes to make sure that the GRO flush API is invoked if there are no
> packets in
> current poll and timer expiry.
>
> app/test-pmd/csumonly.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/app/test-pmd/csumonly.c b/app/test-pmd/csumonly.c
> index c103e54111..42f105ac16 100644
> --- a/app/test-pmd/csumonly.c
> +++ b/app/test-pmd/csumonly.c
> @@ -863,16 +863,24 @@ pkt_burst_checksum_forward(struct fwd_stream *fs)
>
> /* receive a burst of packet */
> nb_rx = common_fwd_stream_receive(fs, pkts_burst,
> nb_pkt_per_burst);
> - if (unlikely(nb_rx == 0))
> + if (unlikely(nb_rx == 0)) {
> +#ifdef RTE_LIB_GRO
> + gro_enable = gro_ports[fs->rx_port].enable;
> + if (unlikely(gro_enable && (gro_flush_cycles !=
> GRO_DEFAULT_FLUSH_CYCLES))) {
> + goto init;
> + } else {
> + return false;
> + }
> +#else
> return false;
> +#endif
> + }
>
> +init:
> rx_bad_ip_csum = 0;
> rx_bad_l4_csum = 0;
> rx_bad_outer_l4_csum = 0;
> rx_bad_outer_ip_csum = 0;
> -#ifdef RTE_LIB_GRO
> - gro_enable = gro_ports[fs->rx_port].enable;
> -#endif
>
> txp = &ports[fs->tx_port];
> tx_offloads = txp->dev_conf.txmode.offloads;
> --
> 2.25.1
> >>Please ignore this patch, this has an issue will raise a new one.
>
>
[-- Attachment #2: Type: text/html, Size: 2565 bytes --]
next prev parent reply other threads:[~2024-01-17 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 19:52 Kumara Parameshwaran
2024-01-17 19:57 ` kumaraparameshwaran rathinavel [this message]
2024-01-17 20:14 ` [PATCH v2] " Kumara Parameshwaran
2024-01-17 20:20 ` [PATCH v3] " Kumara Parameshwaran
2024-01-17 20:24 ` [PATCH v4] " Kumara Parameshwaran
2024-01-18 8:36 ` [PATCH v5] " Kumara Parameshwaran
2024-02-07 22:57 ` Ferruh Yigit
2024-02-11 4:55 ` [PATCH v6] " Kumara Parameshwaran
2024-02-12 15:05 ` Ferruh Yigit
2024-02-16 3:40 ` [PATCH v7] app/testpmd : fix " Kumara Parameshwaran
2024-02-16 4:13 ` Stephen Hemminger
2024-02-16 3:47 ` [PATCH v8] " Kumara Parameshwaran
2024-02-16 13:56 ` Ferruh Yigit
2024-02-21 18:02 ` Ferruh Yigit
2024-02-22 11:15 ` kumaraparameshwaran rathinavel
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='CANxNyaszTnDf4kLBC2xgVtyrtu3aCm8G=nH19ZRUzwerqkx1EQ@mail.gmail.com' \
--to=kumaraparamesh92@gmail.com \
--cc=dev@dpdk.org \
--cc=hujiayu.hu@foxmail.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).