All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maxim Mikityanskiy <maximmi@mellanox.com>
Cc: davem@davemloft.net, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
	jiri@resnulli.us, dsahern@gmail.com, saeedm@nvidia.com,
	kuba@kernel.org, tariqt@nvidia.com, yossiku@nvidia.com,
	maximmi@nvidia.com, dan.carpenter@oracle.com,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/5] HTB offload
Date: Sat, 23 Jan 2021 06:10:23 +0000	[thread overview]
Message-ID: <161138222368.25900.11180760224277767499.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210119120815.463334-1-maximmi@mellanox.com>

Hello:

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

On Tue, 19 Jan 2021 14:08:10 +0200 you wrote:
> This series adds support for HTB offload to the HTB qdisc, and adds
> usage to mlx5 driver.
> 
> The previous RFCs are available at [1], [2].
> 
> The feature is intended to solve the performance bottleneck caused by
> the single lock of the HTB qdisc, which prevents it from scaling well.
> The HTB algorithm itself is offloaded to the device, eliminating the
> need to take the root lock of HTB on every packet. Classification part
> is done in clsact (still in software) to avoid acquiring the lock, which
> imposes a limitation that filters can target only leaf classes.
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/5] net: sched: Add multi-queue support to sch_tree_lock
    https://git.kernel.org/netdev/net-next/c/ca1e4ab19993
  - [net-next,v4,2/5] net: sched: Add extack to Qdisc_class_ops.delete
    https://git.kernel.org/netdev/net-next/c/4dd78a73738a
  - [net-next,v4,3/5] sch_htb: Hierarchical QoS hardware offload
    https://git.kernel.org/netdev/net-next/c/d03b195b5aa0
  - [net-next,v4,4/5] sch_htb: Stats for offloaded HTB
    https://git.kernel.org/netdev/net-next/c/83271586249c
  - [net-next,v4,5/5] net/mlx5e: Support HTB offload
    https://git.kernel.org/netdev/net-next/c/214baf22870c

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-01-23  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 12:08 [PATCH net-next v4 0/5] HTB offload Maxim Mikityanskiy
2021-01-19 12:08 ` [PATCH net-next v4 1/5] net: sched: Add multi-queue support to sch_tree_lock Maxim Mikityanskiy
2021-01-19 12:08 ` [PATCH net-next v4 2/5] net: sched: Add extack to Qdisc_class_ops.delete Maxim Mikityanskiy
2021-01-19 12:08 ` [PATCH net-next v4 3/5] sch_htb: Hierarchical QoS hardware offload Maxim Mikityanskiy
2021-01-19 12:08 ` [PATCH net-next v4 4/5] sch_htb: Stats for offloaded HTB Maxim Mikityanskiy
2021-01-19 12:08 ` [PATCH net-next v4 5/5] net/mlx5e: Support HTB offload Maxim Mikityanskiy
2021-01-23  6:10 ` 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=161138222368.25900.11180760224277767499.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=maximmi@mellanox.com \
    --cc=maximmi@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yossiku@nvidia.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.