From: Stephen Hemminger <stephen@networkplumber.org>
To: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Cc: hujiayu.hu@foxmail.com, dev@dpdk.org
Subject: Re: [PATCH v11] gro: fix reordering of packets in GRO layer
Date: Sun, 7 Jan 2024 09:20:20 -0800 [thread overview]
Message-ID: <20240107092020.371d466d@hermes.local> (raw)
In-Reply-To: <20240107112920.521184-1-kumaraparamesh92@gmail.com>
On Sun, 7 Jan 2024 16:59:20 +0530
Kumara Parameshwaran <kumaraparamesh92@gmail.com> wrote:
> + /* Return early if the TCP flags are not handled in GRO layer */
> + if (tcp_hdr->tcp_flags & (~(VALID_GRO_TCP_FLAGS)))
Nit, lots of extra paren here. Could be:
if (tcp_hdr->tcp_flags & ~VALID_GRO_TCP_FLAGS)
> + if (find == 1) {
> + /*
> + * Any packet with additional flags like PSH,FIN should be processed
> + * and flushed immediately.
> + * Hence marking the start time to 0, so that the packets will be flushed
> + * immediately in timer mode.
> + */
> + if (tcp_hdr->tcp_flags & (RTE_TCP_ACK_FLAG | RTE_TCP_PSH_FLAG | RTE_TCP_FIN_FLAG)) {
> + if (tcp_hdr->tcp_flags != RTE_TCP_ACK_FLAG)
> + tbl->items[item_start_idx].start_time = 0;
> + return process_tcp_item(pkt, tcp_hdr, tcp_dl, tbl->items,
> + tbl->flows[i].start_index,
> + &tbl->item_num, tbl->max_item_num,
> + ip_id, is_atomic, start_time);
> + } else {
> + return -1;
> + }
> + }
Reordering this conditional would keep code from being so indented.
> - delete_tcp_item(tbl->items, item_idx, &tbl->item_num, INVALID_ARRAY_INDEX);
> + delete_tcp_item(tbl->items, item_idx, &tbl->item_num,
> + INVALID_ARRAY_INDEX);
> return -1;
This change is unnecessary, max line length in DPDK is 100 characters for readability.
> return 0;
> + } else {
> + return -1;
> }
>
> - return process_tcp_item(pkt, tcp_hdr, tcp_dl, tbl->items, tbl->flows[i].start_index,
> - &tbl->item_num, tbl->max_item_num,
> - ip_id, is_atomic, start_time);
> + return -1;
> }
Since end of else and end of function both return -1, the else clause is unnecessary.
next prev parent reply other threads:[~2024-01-07 17:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 10:18 [PATCH] gro : fix reordering of packets in GRO library Kumara Parameshwaran
2022-10-13 10:20 ` kumaraparameshwaran rathinavel
2022-10-28 8:09 ` [PATCH v2] " Kumara Parameshwaran
2022-10-28 8:27 ` [PATCH v3] " Kumara Parameshwaran
2022-10-28 9:51 ` [PATCH v4] " Kumara Parameshwaran
2022-11-01 7:05 ` [PATCH v5] " Kumara Parameshwaran
2023-06-19 13:25 ` Thomas Monjalon
2023-06-20 7:35 ` Hu, Jiayu
2023-06-21 8:47 ` kumaraparameshwaran rathinavel
2023-06-30 11:32 ` kumaraparameshwaran rathinavel
2023-12-08 17:54 ` [PATCH v6] gro: fix reordering of packets in GRO layer Kumara Parameshwaran
2023-12-08 18:05 ` [PATCH v7] " Kumara Parameshwaran
2023-12-08 18:12 ` [PATCH v8] " Kumara Parameshwaran
2023-12-08 18:17 ` [PATCH v9] " Kumara Parameshwaran
2024-01-04 15:49 ` 胡嘉瑜
2024-01-07 11:21 ` [PATCH v10] " Kumara Parameshwaran
2024-01-07 11:29 ` [PATCH v11] " Kumara Parameshwaran
2024-01-07 17:20 ` Stephen Hemminger [this message]
2024-01-08 16:11 ` kumaraparameshwaran rathinavel
2024-01-08 15:50 ` [PATCH v12] " Kumara Parameshwaran
2024-01-08 16:04 ` [PATCH v13] " Kumara Parameshwaran
2024-01-16 14:28 ` 胡嘉瑜
2024-02-12 14:30 ` Thomas Monjalon
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=20240107092020.371d466d@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hujiayu.hu@foxmail.com \
--cc=kumaraparamesh92@gmail.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).