From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Michael Chan <michael.chan@broadcom.com>,
Parav Pandit <parav@nvidia.com>
Cc: <aelior@marvell.com>, <skalluru@marvell.com>,
<manishc@marvell.com>, <netdev@vger.kernel.org>,
<edumazet@google.com>, <davem@davemloft.net>, <kuba@kernel.org>,
<pabeni@redhat.com>, <dsahern@kernel.org>
Subject: Re: [PATCH net-next] tcp: Make GRO completion function inline
Date: Mon, 3 Jul 2023 18:51:13 +0200 [thread overview]
Message-ID: <f25406bd-71b5-79e4-80f7-66c345341504@intel.com> (raw)
In-Reply-To: <CACKFLi=nD76sHPFALg8dzR6Oj2CDGsZqbjY1gS_9ZKdo-KJrHQ@mail.gmail.com>
From: Michael Chan <michael.chan@broadcom.com>
Date: Sat, 1 Jul 2023 16:09:53 -0700
> On Sun, Jun 11, 2023 at 7:08 AM Parav Pandit <parav@nvidia.com> wrote:
>>
>> 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?
>>
>> ---
>
> Sorry for the delay. It works fine on bnxt NICs running hardware GRO.
> No noticeable changes in throughput or CPU utilization running simple
> netperf. Thanks.
>
> Tested-by: Michael Chan <michael.chan@broadcom.com>
> Reviewed-by: Michael Chan <michael.chan@broadcom.com>
Why is this needed then if it gives nothing? :D
Thanks,
Olek
next prev parent reply other threads:[~2023-07-03 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 14:07 [PATCH net-next] tcp: Make GRO completion function inline Parav Pandit
2023-07-01 23:09 ` Michael Chan
2023-07-03 16:51 ` Alexander Lobakin [this message]
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=f25406bd-71b5-79e4-80f7-66c345341504@intel.com \
--to=aleksander.lobakin@intel.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=parav@nvidia.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