From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Ido Schimmel <idosch@idosch.org>,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com,
xiyou.wangcong@gmail.com, victor@mojatatu.com,
pctammela@mojatatu.com, mleitner@redhat.com, vladbu@nvidia.com,
paulb@nvidia.com, Petr Machata <petrm@nvidia.com>
Subject: Re: [patch net-next] net: sched: move block device tracking into tcf_block_get/put_ext()
Date: Thu, 11 Jan 2024 17:27:29 +0100 [thread overview]
Message-ID: <ZaAW8fRkfcDmfFCn@nanopsycho> (raw)
In-Reply-To: <CAM0EoMkpzsEWXMw27xgsfzwA2g4CNeDYQ9niTJAkgu3=Kgp81g@mail.gmail.com>
Thu, Jan 11, 2024 at 04:42:55PM CET, jhs@mojatatu.com wrote:
>On Thu, Jan 11, 2024 at 10:40 AM Jamal Hadi Salim <jhs@mojatatu.com> wrote:
>>
>> On Wed, Jan 10, 2024 at 7:10 AM Ido Schimmel <idosch@idosch.org> wrote:
>> >
>> > On Thu, Jan 04, 2024 at 01:58:44PM +0100, Jiri Pirko wrote:
>> > > diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
>> > > index adf5de1ff773..253b26f2eddd 100644
>> > > --- a/net/sched/cls_api.c
>> > > +++ b/net/sched/cls_api.c
>> > > @@ -1428,6 +1428,7 @@ int tcf_block_get_ext(struct tcf_block **p_block, struct Qdisc *q,
>> > > struct tcf_block_ext_info *ei,
>> > > struct netlink_ext_ack *extack)
>> > > {
>> > > + struct net_device *dev = qdisc_dev(q);
>> > > struct net *net = qdisc_net(q);
>> > > struct tcf_block *block = NULL;
>> > > int err;
>> > > @@ -1461,9 +1462,18 @@ int tcf_block_get_ext(struct tcf_block **p_block, struct Qdisc *q,
>> > > if (err)
>> > > goto err_block_offload_bind;
>> > >
>> > > + if (tcf_block_shared(block)) {
>> > > + err = xa_insert(&block->ports, dev->ifindex, dev, GFP_KERNEL);
>> > > + if (err) {
>> > > + NL_SET_ERR_MSG(extack, "block dev insert failed");
>> > > + goto err_dev_insert;
>> > > + }
>> > > + }
>> >
>> > While this patch fixes the original issue, it creates another one:
>> >
>> > # ip link add name swp1 type dummy
>> > # tc qdisc replace dev swp1 root handle 10: prio bands 8 priomap 7 6 5 4 3 2 1
>> > # tc qdisc add dev swp1 parent 10:8 handle 108: red limit 1000000 min 200000 max 200001 probability 1.0 avpkt 8000 burst 38 qevent early_drop block 10
>> > RED: set bandwidth to 10Mbit
>> > # tc qdisc add dev swp1 parent 10:7 handle 107: red limit 1000000 min 500000 max 500001 probability 1.0 avpkt 8000 burst 63 qevent early_drop block 10
>> > RED: set bandwidth to 10Mbit
>> > Error: block dev insert failed.
>> >
>>
>>
>> +cc Petr
>> We'll add a testcase on tdc - it doesnt seem we have any for qevents.
>> If you have others that are related let us know.
>> But how does this work? I see no mention of block on red code and i
>> see no mention of block on the reproducer above.
>
>Context: Yes, i see it on red setup but i dont see any block being setup.
>Also: Is it only Red or other qdiscs could behave this way?
Just red.
>
>cheers,
>jamal
>> Are the qevents exception packets from the hardware? Is there a good
>> description of what qevents do?
>>
>> cheers,
>> jamal
>>
>>
>> > The reproducer does not fail if I revert this patch and apply Victor's
>> > [1] instead.
>> >
>> > [1] https://lore.kernel.org/netdev/20231231172320.245375-1-victor@mojatatu.com/
>> >
>> > > +
>> > > *p_block = block;
>> > > return 0;
>> > >
>> > > +err_dev_insert:
>> > > err_block_offload_bind:
>> > > tcf_chain0_head_change_cb_del(block, ei);
>> > > err_chain0_head_change_cb_add:
prev parent reply other threads:[~2024-01-11 16:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 12:58 [patch net-next] net: sched: move block device tracking into tcf_block_get/put_ext() Jiri Pirko
2024-01-04 14:32 ` Ido Schimmel
2024-01-04 16:10 ` Jamal Hadi Salim
2024-01-04 18:03 ` Jiri Pirko
2024-01-04 18:22 ` Jamal Hadi Salim
2024-01-05 11:24 ` Jiri Pirko
2024-01-05 11:51 ` Pedro Tammela
2024-01-06 11:14 ` Jiri Pirko
2024-01-06 11:49 ` Jamal Hadi Salim
2024-01-04 19:26 ` Victor Nogueira
2024-01-04 19:36 ` Jamal Hadi Salim
2024-01-05 11:20 ` patchwork-bot+netdevbpf
2024-01-10 12:09 ` Ido Schimmel
2024-01-10 14:08 ` Jiri Pirko
2024-01-10 16:17 ` Jiri Pirko
2024-01-11 8:51 ` Ido Schimmel
2024-01-11 15:40 ` Jamal Hadi Salim
2024-01-11 15:42 ` Jamal Hadi Salim
2024-01-11 16:17 ` Petr Machata
2024-01-11 19:55 ` Jamal Hadi Salim
2024-01-11 21:44 ` Petr Machata
2024-01-12 14:47 ` Jamal Hadi Salim
2024-01-12 15:37 ` Petr Machata
2024-01-15 21:02 ` Jamal Hadi Salim
2024-01-16 10:15 ` Petr Machata
2024-01-17 20:44 ` Jamal Hadi Salim
2024-01-19 16:28 ` Petr Machata
2024-01-21 18:32 ` Jamal Hadi Salim
2024-01-11 16:27 ` Jiri Pirko [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=ZaAW8fRkfcDmfFCn@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@idosch.org \
--cc=jhs@mojatatu.com \
--cc=kuba@kernel.org \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulb@nvidia.com \
--cc=pctammela@mojatatu.com \
--cc=petrm@nvidia.com \
--cc=victor@mojatatu.com \
--cc=vladbu@nvidia.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.