All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, toke@redhat.com, kuniyu@google.com,
	willemb@google.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [PATCH v3 net-next 00/14] net_sched: speedup qdisc dequeue
Date: Tue, 25 Nov 2025 15:24:54 +0000	[thread overview]
Message-ID: <176408429448.752950.12216092755277643932.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251121083256.674562-1-edumazet@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 21 Nov 2025 08:32:42 +0000 you wrote:
> Avoid up to two cache line misses in qdisc dequeue() to fetch
> skb_shinfo(skb)->gso_segs/gso_size while qdisc spinlock is held.
> 
> Idea is to cache gso_segs at enqueue time before spinlock is
> acquired, in the first skb cache line, where we already
> have qdisc_skb_cb(skb)->pkt_len.
> 
> [...]

Here is the summary with links:
  - [v3,net-next,01/14] net_sched: make room for (struct qdisc_skb_cb)->pkt_segs
    https://git.kernel.org/netdev/net-next/c/b2a38f6df9da
  - [v3,net-next,02/14] net: init shinfo->gso_segs from qdisc_pkt_len_init()
    https://git.kernel.org/netdev/net-next/c/be1b70ab21cb
  - [v3,net-next,03/14] net_sched: initialize qdisc_skb_cb(skb)->pkt_segs in qdisc_pkt_len_init()
    https://git.kernel.org/netdev/net-next/c/874c1928d372
  - [v3,net-next,04/14] net: use qdisc_pkt_len_segs_init() in sch_handle_ingress()
    https://git.kernel.org/netdev/net-next/c/f9e00e51e391
  - [v3,net-next,05/14] net_sched: use qdisc_skb_cb(skb)->pkt_segs in bstats_update()
    https://git.kernel.org/netdev/net-next/c/2773cb0b3120
  - [v3,net-next,06/14] net_sched: cake: use qdisc_pkt_segs()
    https://git.kernel.org/netdev/net-next/c/c5d34f4583ea
  - [v3,net-next,07/14] net_sched: add Qdisc_read_mostly and Qdisc_write groups
    https://git.kernel.org/netdev/net-next/c/ad50d5a3fc20
  - [v3,net-next,08/14] net_sched: sch_fq: move qdisc_bstats_update() to fq_dequeue_skb()
    https://git.kernel.org/netdev/net-next/c/3c1100f042c0
  - [v3,net-next,09/14] net_sched: sch_fq: prefetch one skb ahead in dequeue()
    https://git.kernel.org/netdev/net-next/c/2f9babc04d74
  - [v3,net-next,10/14] net: prefech skb->priority in __dev_xmit_skb()
    https://git.kernel.org/netdev/net-next/c/b2e9821cff6c
  - [v3,net-next,11/14] net: annotate a data-race in __dev_xmit_skb()
    https://git.kernel.org/netdev/net-next/c/4792c3a4c147
  - [v3,net-next,12/14] net_sched: add tcf_kfree_skb_list() helper
    https://git.kernel.org/netdev/net-next/c/0170d7f47c8b
  - [v3,net-next,13/14] net_sched: add qdisc_dequeue_drop() helper
    https://git.kernel.org/netdev/net-next/c/191ff13e42a7
  - [v3,net-next,14/14] net_sched: use qdisc_dequeue_drop() in cake, codel, fq_codel
    https://git.kernel.org/netdev/net-next/c/a6efc273ab82

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-25 15:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  8:32 [PATCH v3 net-next 00/14] net_sched: speedup qdisc dequeue Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 01/14] net_sched: make room for (struct qdisc_skb_cb)->pkt_segs Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 02/14] net: init shinfo->gso_segs from qdisc_pkt_len_init() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 03/14] net_sched: initialize qdisc_skb_cb(skb)->pkt_segs in qdisc_pkt_len_init() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 04/14] net: use qdisc_pkt_len_segs_init() in sch_handle_ingress() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 05/14] net_sched: use qdisc_skb_cb(skb)->pkt_segs in bstats_update() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 06/14] net_sched: cake: use qdisc_pkt_segs() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 07/14] net_sched: add Qdisc_read_mostly and Qdisc_write groups Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 08/14] net_sched: sch_fq: move qdisc_bstats_update() to fq_dequeue_skb() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 09/14] net_sched: sch_fq: prefetch one skb ahead in dequeue() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 10/14] net: prefech skb->priority in __dev_xmit_skb() Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 11/14] net: annotate a data-race " Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 12/14] net_sched: add tcf_kfree_skb_list() helper Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 13/14] net_sched: add qdisc_dequeue_drop() helper Eric Dumazet
2025-11-21  8:32 ` [PATCH v3 net-next 14/14] net_sched: use qdisc_dequeue_drop() in cake, codel, fq_codel Eric Dumazet
2025-11-25 15:24 ` patchwork-bot+netdevbpf [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=176408429448.752950.12216092755277643932.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=toke@redhat.com \
    --cc=willemb@google.com \
    --cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.