public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, kernel-team@cloudflare.com,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Shuah Khan" <shuah@kernel.org>,
	linux-kselftest@vger.kernel.org,
	"Chris Arges" <carges@cloudflare.com>,
	"Mike Freemon" <mfreemon@cloudflare.com>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Jonas Köppeler" <j.koeppeler@tu-berlin.de>,
	"Breno Leitao" <leitao@debian.org>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"Stanislav Fomichev" <sdf@fomichev.me>,
	bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] veth: add Byte Queue Limits (BQL) support
Date: Fri, 1 May 2026 09:28:49 +0200	[thread overview]
Message-ID: <f9292ffc-e62d-4048-879b-042ec4d7d0db@kernel.org> (raw)
In-Reply-To: <20260430185825.43b2d0aa@kernel.org>



On 01/05/2026 03.58, Jakub Kicinski wrote:
> On Wed, 29 Apr 2026 19:20:27 +0200 hawk@kernel.org wrote:
>> This series adds BQL (Byte Queue Limits) to the veth driver, reducing
>> latency by dynamically limiting in-flight packets in the ptr_ring and
>> moving buffering into the qdisc where AQM algorithms can act on it.
> 
> Does not apply (am I remembering right that it's not the first time
> this series doesn't apply?)

Rebased posted
  V4: https://lore.kernel.org/all/20260501071633.644353-1-hawk@kernel.org/

The conflict was on tools/testing/selftests/net/config for a change 
applied 16 Apr, and I send patchset 29 Apr.  So, yes it seems I forgot 
to rebase for that period, sorry.

--Jesper


      reply	other threads:[~2026-05-01  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 17:20 [PATCH net-next v3 0/5] veth: add Byte Queue Limits (BQL) support hawk
2026-04-29 17:20 ` [PATCH net-next v3 1/5] net: add dev->bql flag to allow BQL sysfs for IFF_NO_QUEUE devices hawk
2026-04-29 17:20 ` [PATCH net-next v3 2/5] veth: implement Byte Queue Limits (BQL) for latency reduction hawk
2026-04-29 17:20 ` [PATCH net-next v3 3/5] veth: add tx_timeout watchdog as BQL safety net hawk
2026-04-29 17:20 ` [PATCH net-next v3 4/5] net: sched: add timeout count to NETDEV WATCHDOG message hawk
2026-04-29 17:20 ` [PATCH net-next v3 5/5] selftests: net: add veth BQL stress test hawk
2026-05-01  2:00   ` Jakub Kicinski
2026-05-01  7:03     ` Jesper Dangaard Brouer
2026-05-01  8:42   ` Breno Leitao
2026-05-01  1:58 ` [PATCH net-next v3 0/5] veth: add Byte Queue Limits (BQL) support Jakub Kicinski
2026-05-01  7:28   ` Jesper Dangaard Brouer [this message]

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=f9292ffc-e62d-4048-879b-042ec4d7d0db@kernel.org \
    --to=hawk@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=carges@cloudflare.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=j.koeppeler@tu-berlin.de \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@cloudflare.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mfreemon@cloudflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=toke@toke.dk \
    /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