From: David Ahern <dsahern@gmail.com>
To: Maxim Mikityanskiy <maximmi@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
Yossi Kuperman <yossiku@nvidia.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
netdev@vger.kernel.org, Maxim Mikityanskiy <maximmi@mellanox.com>
Subject: Re: [PATCH iproute2-next] tc/htb: Hierarchical QoS hardware offload
Date: Tue, 2 Feb 2021 08:32:06 -0700 [thread overview]
Message-ID: <7ddf3098-a190-95ae-0536-dc664580e298@gmail.com> (raw)
In-Reply-To: <01ce90dc-9880-ccad-cce4-e13dc22f8118@nvidia.com>
On 2/2/21 4:46 AM, Maxim Mikityanskiy wrote:
> On 2021-01-29 18:05, David Ahern wrote:
>> On 12/15/20 12:42 AM, Maxim Mikityanskiy wrote:
>>> This commit adds support for configuring HTB in offload mode. HTB
>>> offload eliminates the single qdisc lock in the datapath and offloads
>>> the algorithm to the NIC. The new 'offload' parameter is added to
>>> enable this mode:
>>>
>>> # tc qdisc replace dev eth0 root handle 1: htb offload
>>>
>>> Classes are created as usual, but filters should be moved to clsact for
>>> lock-free classification (filters attached to HTB itself are not
>>> supported in the offload mode):
>>>
>>> # tc filter add dev eth0 egress protocol ip flower dst_port 80
>>> action skbedit priority 1:10
>>
>> please add the dump in both stdout and json here.
>
> Do you mean to add example output to the commit message?
yes.
>>> diff --git a/tc/q_htb.c b/tc/q_htb.c
>>> index c609e974..fd11dad6 100644
>>> --- a/tc/q_htb.c
>>> +++ b/tc/q_htb.c
>>> @@ -30,11 +30,12 @@
>>> static void explain(void)
>>> {
>>> fprintf(stderr, "Usage: ... qdisc add ... htb [default N] [r2q
>>> N]\n"
>>> - " [direct_qlen P]\n"
>>> + " [direct_qlen P] [offload]\n"
>>> " default minor id of class to which unclassified packets
>>> are sent {0}\n"
>>> " r2q DRR quantums are computed as rate in Bps/r2q
>>> {10}\n"
>>> " debug string of 16 numbers each 0-3 {0}\n\n"
>>> " direct_qlen Limit of the direct queue {in packets}\n"
>>> + " offload hardware offload\n"
>>
>> why 'offload hardware offload'? does not make sense to me and
>
> "offload" is a new parameter, and "hardware offload" is the description,
> just like the other parameters above.
>
>> you don't
>> reference hardware below.
>
> Where should I reference it?
I see now. More words are needed to make it clear 'hardware offload' is
the explanation of offload. As it is, the words run together as 'offload
hardware offload' which is the source of my confusion.
prev parent reply other threads:[~2021-02-02 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 7:42 [PATCH iproute2-next] tc/htb: Hierarchical QoS hardware offload Maxim Mikityanskiy
2020-12-15 7:42 ` [PATCH net-next v3 0/4] HTB offload Maxim Mikityanskiy
2020-12-15 7:42 ` [PATCH net-next v3 1/4] net: sched: Add multi-queue support to sch_tree_lock Maxim Mikityanskiy
2020-12-15 7:42 ` [PATCH net-next v3 2/4] sch_htb: Hierarchical QoS hardware offload Maxim Mikityanskiy
2020-12-22 1:17 ` Jakub Kicinski
2021-01-04 21:55 ` Maxim Mikityanskiy
2020-12-15 7:42 ` [PATCH net-next v3 3/4] sch_htb: Stats for offloaded HTB Maxim Mikityanskiy
2020-12-15 7:42 ` [PATCH net-next v3 4/4] net/mlx5e: Support HTB offload Maxim Mikityanskiy
2020-12-15 22:26 ` [PATCH iproute2-next] tc/htb: Hierarchical QoS hardware offload Stephen Hemminger
[not found] ` <8c818766-ec3f-4c0b-f737-ec558613b946@gmail.com>
2021-02-02 11:46 ` Maxim Mikityanskiy
2021-02-02 15:32 ` David Ahern [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=7ddf3098-a190-95ae-0536-dc664580e298@gmail.com \
--to=dsahern@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--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.