From: Parav Pandit <parav@nvidia.com>
To: <michael.chan@broadcom.com>, <aelior@marvell.com>,
<skalluru@marvell.com>, <manishc@marvell.com>,
<netdev@vger.kernel.org>
Cc: <edumazet@google.com>, <davem@davemloft.net>, <kuba@kernel.org>,
<pabeni@redhat.com>, <dsahern@kernel.org>,
Parav Pandit <parav@nvidia.com>
Subject: [PATCH net-next] tcp: Make GRO completion function inline
Date: Sun, 11 Jun 2023 17:07:56 +0300 [thread overview]
Message-ID: <20230611140756.1203607-1-parav@nvidia.com> (raw)
At 100G link speed, with 1500 MTU, at 8.2 mpps, if device does GRO for
64K message size, currently it results in ~190k calls to
tcp_gro_complete() in data path.
Inline this small routine to avoid above number of function calls.
Suggested-by: David Ahern <dsahern@kernel.org>
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
This patch is untested as I do not have the any of the 3 hw devices
calling this routine.
qede, bnxt and bnx2x maintainers,
Can you please verify it with your devices if it reduces cpu
utilization marginally or it stays same or has some side effects?
---
include/net/tcp.h | 19 ++++++++++++++++++-
net/ipv4/tcp_offload.c | 18 ------------------
2 files changed, 18 insertions(+), 19 deletions(-)
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 49611af31bb7..e6e0a7125618 100644
--- a/include/net/tcp.h
+++ b/include/net/tcp.h
@@ -40,6 +40,7 @@
#include <net/inet_ecn.h>
#include <net/dst.h>
#include <net/mptcp.h>
+#include <net/gro.h>
#include <linux/seq_file.h>
#include <linux/memcontrol.h>
@@ -2043,7 +2044,23 @@ INDIRECT_CALLABLE_DECLARE(int tcp4_gro_complete(struct sk_buff *skb, int thoff))
INDIRECT_CALLABLE_DECLARE(struct sk_buff *tcp4_gro_receive(struct list_head *head, struct sk_buff *skb));
INDIRECT_CALLABLE_DECLARE(int tcp6_gro_complete(struct sk_buff *skb, int thoff));
INDIRECT_CALLABLE_DECLARE(struct sk_buff *tcp6_gro_receive(struct list_head *head, struct sk_buff *skb));
-void tcp_gro_complete(struct sk_buff *skb);
+
+static inline void tcp_gro_complete(struct sk_buff *skb)
+{
+ struct tcphdr *th = tcp_hdr(skb);
+
+ skb->csum_start = (unsigned char *)th - skb->head;
+ skb->csum_offset = offsetof(struct tcphdr, check);
+ skb->ip_summed = CHECKSUM_PARTIAL;
+
+ skb_shinfo(skb)->gso_segs = NAPI_GRO_CB(skb)->count;
+
+ if (th->cwr)
+ skb_shinfo(skb)->gso_type |= SKB_GSO_TCP_ECN;
+
+ if (skb->encapsulation)
+ skb->inner_transport_header = skb->transport_header;
+}
void __tcp_v4_send_check(struct sk_buff *skb, __be32 saddr, __be32 daddr);
diff --git a/net/ipv4/tcp_offload.c b/net/ipv4/tcp_offload.c
index 8311c38267b5..5628d6007d43 100644
--- a/net/ipv4/tcp_offload.c
+++ b/net/ipv4/tcp_offload.c
@@ -296,24 +296,6 @@ struct sk_buff *tcp_gro_receive(struct list_head *head, struct sk_buff *skb)
return pp;
}
-void tcp_gro_complete(struct sk_buff *skb)
-{
- struct tcphdr *th = tcp_hdr(skb);
-
- skb->csum_start = (unsigned char *)th - skb->head;
- skb->csum_offset = offsetof(struct tcphdr, check);
- skb->ip_summed = CHECKSUM_PARTIAL;
-
- skb_shinfo(skb)->gso_segs = NAPI_GRO_CB(skb)->count;
-
- if (th->cwr)
- skb_shinfo(skb)->gso_type |= SKB_GSO_TCP_ECN;
-
- if (skb->encapsulation)
- skb->inner_transport_header = skb->transport_header;
-}
-EXPORT_SYMBOL(tcp_gro_complete);
-
INDIRECT_CALLABLE_SCOPE
struct sk_buff *tcp4_gro_receive(struct list_head *head, struct sk_buff *skb)
{
--
2.26.2
next reply other threads:[~2023-06-11 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 14:07 Parav Pandit [this message]
2023-07-01 23:09 ` [PATCH net-next] tcp: Make GRO completion function inline Michael Chan
2023-07-03 16:51 ` Alexander Lobakin
2023-07-03 17:00 ` Michael Chan
2023-07-03 17:29 ` David Ahern
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=20230611140756.1203607-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skalluru@marvell.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