From: Jiri Pirko <jiri@resnulli.us>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: "Jiri Pirko" <jiri@mellanox.com>,
"Linux Kernel Network Developers" <netdev@vger.kernel.org>,
"Paweł Staszewski" <pstaszewski@itcare.pl>
Subject: Re: Fwd: u32 ht filters
Date: Mon, 12 Feb 2018 14:23:52 +0100 [thread overview]
Message-ID: <20180212132352.GA2153@nanopsycho> (raw)
In-Reply-To: <CAM_iQpXwKmuuDaHWuJ+E60P2pr00tsVr2+p_hY++D7Vi8Hbavw@mail.gmail.com>
Sat, Feb 10, 2018 at 09:41:57PM CET, xiyou.wangcong@gmail.com wrote:
>On Wed, Feb 7, 2018 at 11:38 PM, Jiri Pirko <jiri@resnulli.us> wrote:
>> Thu, Feb 08, 2018 at 12:08:36AM CET, xiyou.wangcong@gmail.com wrote:
>>>On Tue, Feb 6, 2018 at 11:01 PM, Jiri Pirko <jiri@resnulli.us> wrote:
>>>> Wed, Feb 07, 2018 at 06:09:15AM CET, xiyou.wangcong@gmail.com wrote:
>>>>>Hi, Jiri
>>>>>
>>>>>Your commit 7fa9d974f3c2a016b9accb18f4ee2ed2a738585c
>>>>>breaks the tc script by Paweł. Please find below for details.
>>>>
>>>> Did you do the bisection?
>>>> The commit just uses block struct instead of q, but since they
>>>> are in 1:1 relation, that should be equvivalent. So basically you still
>>>> have per-qdisc hashtables for u32.
>>>
>>>Well, at least the following fixes the problem here. But I am not sure
>>>if it is expected too for shared block among multiple qdiscs.
>>
>> For shared block, block->q is null.
>
>According to this comment:
>/* block_index not 0 means the shared block is requested */
>
>and the code,
>
> if (!block) {
> block = tcf_block_create(net, q, extack);
>
>block->q is set to q, and q is always non-NULL AFAIU.
Yep, that is a bug. Fixing it now.
>
>Also, I don't know if it is intended, but block->q always points to
>the parent qdisc rather than the qdisc attached to a class.
You are right. That is incorrect. Fixing now.
>
>
>>>
>>>
>>>@@ -338,7 +330,7 @@ static struct hlist_head *tc_u_common_hash;
>>>
>>> static unsigned int tc_u_hash(const struct tcf_proto *tp)
>>> {
>>>- return hash_ptr(tp->chain->block, U32_HASH_SHIFT);
>>>+ return hash_ptr(tp->chain->block->q, U32_HASH_SHIFT);
>>> }
>>>
>>> static struct tc_u_common *tc_u_common_find(const struct tcf_proto *tp)
>>>@@ -348,7 +340,7 @@ static struct tc_u_common *tc_u_common_find(const
>>>struct tcf_proto *tp)
>>>
>>> h = tc_u_hash(tp);
>>> hlist_for_each_entry(tc, &tc_u_common_hash[h], hnode) {
>>>- if (tc->block == tp->chain->block)
>>>+ if (tc->block->q == tp->chain->block->q)
>>
>> :O I don't get it. tc->block is pointer, tc->block->q is pointer. And
>> they are different at the same time for non-shared block.
>
>If you look into Pawel's script, a new block is created for each class
>therefore a different tc_u_common is created which causes the
>ht 9:22 can't be found.
Yeah :/ this tc_u_common thing is going to haunt me. This is resolvable
now by using block->q. There is no support for block sharing for other
qdiscs than ingress and clsact so we don't have to take care of the
multi-class&block sharing now. Will fix.
Thanks!
next prev parent reply other threads:[~2018-02-12 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c8f997d-339c-5088-0bb5-124e9f55f02d@itcare.pl>
2018-02-07 5:09 ` Fwd: u32 ht filters Cong Wang
2018-02-07 7:01 ` Jiri Pirko
2018-02-07 23:08 ` Cong Wang
2018-02-08 7:38 ` Jiri Pirko
2018-02-10 20:41 ` Cong Wang
2018-02-12 13:23 ` Jiri Pirko [this message]
2018-02-12 15:32 ` Jiri Pirko
2018-02-12 15:51 ` Jiri Pirko
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=20180212132352.GA2153@nanopsycho \
--to=jiri@resnulli.us \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).