From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Simon Horman <horms@kernel.org>,
Neal Cardwell <ncardwell@google.com>,
Willem de Bruijn <willemb@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] tcp: better handle TCP_TX_DELAY on established flows
Date: Tue, 14 Oct 2025 10:04:57 -0700 [thread overview]
Message-ID: <20251014100457.3f6de3e0@kernel.org> (raw)
In-Reply-To: <CANn89iL0ZjuH-YiuBbm2+s_2adQzVUVOi4VYDvwGBXjTBYHb=A@mail.gmail.com>
On Tue, 14 Oct 2025 09:16:23 -0700 Eric Dumazet wrote:
> On Tue, Oct 14, 2025 at 9:06 AM Jakub Kicinski <kuba@kernel.org> wrote:
> > On Tue, 14 Oct 2025 02:40:39 -0700 Eric Dumazet wrote:
> > > Or add a best effort, so that TCP can have some clue, vast majority of
> > > cases is that the batch is 1 skb :)
> >
> > FWIW I don't see an official submission and CI is quite behind
> > so I'll set the test to ignored for now.
>
> You mean this TCP_TX_DELAY patch ? Or the series ?
>
> I will send V2 of the series soon. (I added the test unflake in it)
Great, I wasn't clear whether you'll send a separate fix or v2.
So I disabled the test itself.
Not the patches, patches are still queued.
Sorry for the confusion, our CI is what it is - just carry on as normal
and I'll try to keep up.
next prev parent reply other threads:[~2025-10-14 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 14:59 [PATCH net-next] tcp: better handle TCP_TX_DELAY on established flows Eric Dumazet
2025-10-14 8:22 ` Paolo Abeni
2025-10-14 8:29 ` Eric Dumazet
2025-10-14 8:54 ` Eric Dumazet
2025-10-14 9:37 ` Paolo Abeni
2025-10-14 9:40 ` Eric Dumazet
2025-10-14 16:06 ` Jakub Kicinski
2025-10-14 16:16 ` Eric Dumazet
2025-10-14 17:04 ` Jakub Kicinski [this message]
2025-10-14 9:38 ` Eric Dumazet
2025-10-15 2:34 ` Jakub Kicinski
2025-10-15 5:17 ` Eric Dumazet
2025-10-15 16:00 ` patchwork-bot+netdevbpf
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=20251014100457.3f6de3e0@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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).