Netdev List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Mariusz Klimek <maklimek97@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
	netdev@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, dsahern@kernel.org, idosch@nvidia.com,
	ncardwell@google.com, shuah@kernel.org, kuniyu@google.com,
	alice@isovalent.com, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next 00/10] tcp: support non-GSO jumbograms
Date: Wed, 10 Jun 2026 22:10:49 +0200	[thread overview]
Message-ID: <f926259d-4612-44d2-9711-4a408e41e7f6@redhat.com> (raw)
In-Reply-To: <85eaf82a-28bf-4d3d-958d-1225a7ae9608@gmail.com>

On 6/10/26 4:16 PM, Mariusz Klimek wrote:
> On 6/10/26 00:27, Jakub Kicinski wrote:
>> On Tue, 9 Jun 2026 19:01:02 +0200 Mariusz Klimek wrote:
>>> I understand your concerns and they're reasonable. I would still like to
>>> proceed with this series, though. What can I do for you to consider this
>>> series? Would it help to submit a few less-significant patches first before
>>> resubmitting this patch series? Should I resubmit it as an RFC?
>>
>> AI tools changed how much we value code, but they did not change much
>> about how one joins a community.
> 
> OK, I'll start with smaller patches to establish myself more
> in the community. I am still interested in eventually getting this
> series through as it can speed up workloads relevant to our company.
> Do you think this patch could potentially be considered down the line?

If you are strongly motivated to do progresses in this area, one thing
you could look at is the root cause of the performance difference
between the veth jumbogram and the same size veth big tcp test: I'm
quite surprised some delta is visible there.

Possibly perf can outline some bottle-neck in the big tcp path that
could be ironed-out.

Also it could be interesting if some devices could do H/W GRO based big TCP.

/P


  parent reply	other threads:[~2026-06-10 20:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 16:33 [PATCH net-next 00/10] tcp: support non-GSO jumbograms Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 01/10] ipv6: do not fragment packets into jumbograms Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 02/10] ipv6: allow route exceptions with MTUs above 65535 Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 03/10] ipv6: add jumbo payload option to non-gso jumbograms Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 04/10] tcp: decouple TSO segment length from MSS Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 05/10] tcp: split jumbograms with urgent pointer correctly Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 06/10] tcp: set MSS correctly for PMTU above 65535 Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 07/10] veth: raise the max MTU " Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 08/10] selftests/net: test sending TCP jumbograms over veth Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 09/10] selftests/net: add test cases with MTU above 65535 to big_tcp.sh Mariusz Klimek
2026-06-08 13:07 ` [PATCH net-next 10/10] selftests/net: add jumbogram test case to msg_zerocopy.sh Mariusz Klimek
2026-06-09  1:15 ` [PATCH net-next 00/10] tcp: support non-GSO jumbograms Eric Dumazet
2026-06-09 17:01   ` Mariusz Klimek
2026-06-09 22:27     ` Jakub Kicinski
2026-06-10 14:16       ` Mariusz Klimek
2026-06-10 17:11         ` Eric Dumazet
2026-06-10 20:10         ` Paolo Abeni [this message]
2026-10-05 13:15           ` Mariusz Klimek

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=f926259d-4612-44d2-9711-4a408e41e7f6@redhat.com \
    --to=pabeni@redhat.com \
    --cc=alice@isovalent.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=maklimek97@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=shuah@kernel.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