All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, jhs@mojatatu.com,
	jiri@resnulli.us, xiyou.wangcong@gmail.com, edumazet@google.com
Subject: Re: [PATCH net-next 0/3] net: sched: update default qdisc visibility after Tx queue cnt changes
Date: Wed, 15 Sep 2021 15:20:09 +0000	[thread overview]
Message-ID: <163171920942.21180.16902973034127753411.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210913225332.662291-1-kuba@kernel.org>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Mon, 13 Sep 2021 15:53:29 -0700 you wrote:
> Matthew noticed that number of children reported by mq does not match
> number of queues on reconfigured interfaces. For example if mq is
> instantiated when there is 8 queues it will always show 8 children,
> regardless of config being changed:
> 
>  # ethtool -L eth0 combined 8
>  # tc qdisc replace dev eth0 root handle 100: mq
>  # tc qdisc show dev eth0
>  qdisc mq 100: root
>  qdisc pfifo_fast 0: parent 100:8 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:7 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:6 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:5 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:4 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:3 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:2 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:1 bands 3 priomap 1 2 ...
>  # ethtool -L eth0 combined 1
>  # tc qdisc show dev eth0
>  qdisc mq 100: root
>  qdisc pfifo_fast 0: parent 100:8 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:7 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:6 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:5 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:4 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:3 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:2 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:1 bands 3 priomap 1 2 ...
>  # ethtool -L eth0 combined 32
>  # tc qdisc show dev eth0
>  qdisc mq 100: root
>  qdisc pfifo_fast 0: parent 100:8 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:7 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:6 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:5 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:4 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:3 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:2 bands 3 priomap 1 2 ...
>  qdisc pfifo_fast 0: parent 100:1 bands 3 priomap 1 2 ...
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] net: sched: update default qdisc visibility after Tx queue cnt changes
    https://git.kernel.org/netdev/net-next/c/1e080f17750d
  - [net-next,2/3] netdevsim: add ability to change channel count
    https://git.kernel.org/netdev/net-next/c/2e367522ce6b
  - [net-next,3/3] selftests: net: test ethtool -L vs mq
    https://git.kernel.org/netdev/net-next/c/2d6a58996ee2

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



      parent reply	other threads:[~2021-09-15 15:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 22:53 [PATCH net-next 0/3] net: sched: update default qdisc visibility after Tx queue cnt changes Jakub Kicinski
2021-09-13 22:53 ` [PATCH net-next 1/3] " Jakub Kicinski
2021-09-15 16:31   ` Cong Wang
2021-09-15 19:36     ` Jakub Kicinski
2021-09-17  5:46       ` Cong Wang
2021-09-17 13:08         ` Jakub Kicinski
2021-09-19 23:38           ` Cong Wang
2021-09-13 22:53 ` [PATCH net-next 2/3] netdevsim: add ability to change channel count Jakub Kicinski
2021-09-13 22:53 ` [PATCH net-next 3/3] selftests: net: test ethtool -L vs mq Jakub Kicinski
2021-09-15 15:20 ` 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=163171920942.21180.16902973034127753411.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --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.