From: Cong Wang <firstname.lastname@example.org>
To: Alexei Starovoitov <email@example.com>
Cc: Network Development <firstname.lastname@example.org>,
bpf <email@example.com>, Cong Wang <firstname.lastname@example.org>,
Jamal Hadi Salim <email@example.com>,
Jiri Pirko <firstname.lastname@example.org>
Subject: Re: [RFC Patch net-next v2] net_sched: introduce eBPF based Qdisc
Date: Tue, 28 Sep 2021 22:40:08 -0700 [thread overview]
Message-ID: <CAM_iQpVaVvaEn2ORfyZQ-FN56pCdE4YPa0r2E+VgyZzvEP31cQ@mail.gmail.com> (raw)
On Wed, Sep 22, 2021 at 6:49 PM Alexei Starovoitov
> On Tue, Sep 21, 2021 at 9:13 PM Cong Wang <email@example.com> wrote:
> > "This *incomplete* patch introduces a programmable Qdisc with
> > eBPF. The goal is to make this Qdisc as programmable as possible,
> > that is, to replace as many existing Qdisc's as we can, no matter
> > in tree or out of tree. And we want to make programmer's and researcher's
> > life as easy as possible, so that they don't have to write a complete
> > Qdisc kernel module just to experiment some queuing theory."
> The inspiration was clear and obvious.
> Folks in the thread had the same idea long before your patches came out.
> But it doesn't matter who came up with an idea to implement qdisc in bpf first.
> Everyone in the thread agreed that such a feature would be great to have.
> The point people explicitly highlighted is that qdisc is not only about skbs.
> The queuing concepts (fq, codel, etc) are useful in xdp and non networking
> contexts too.
> That's why approaching the goal with more generic ambitions was requested.
This goal has nothing to do with my goal, I am pretty sure we have
a lot of queues in networking, here I am only interested in Qdisc for
sure. If you need queues in any other place, it is your job, not mine.
More importantly, what's the conflict between these two goals here?
I see none, from your response, it implies we could only have one.
> > If you compare it with V1, V2 explains the use case in more details,
> > which is to target Qdisc writers, not any other. Therefore, the argument
> > of making it out of Qdisc is non-sense, anything outside of Qdisc is
> > not even my target. Of course you can do anything in XDP, but it has
> > absolutely nothing with my goal here: Qdisc.
> Applying queuing discipline to non-skb context may be not your target
> but it's a reasonable and practical request to have. The kernel is not
Your request has nothing to do with TC or Qdisc, nor it has any
conflict at all.
> about solving one person's itch. The kernel has to be optimized for
> all use cases.
What are you talking about? Are you saying we can't add any new
Qdisc simply because you want to a queue in XDP and it is more
> > I also addressed the skb map concern:
> > " 2b) Kernel would lose the visibility of the "queues", as maps are only
> > shared between eBPF programs and user-space. These queues still have to
> > interact with the kernel, for example, kernel wants to reset all queues
> > when we reset the network interface, kernel wants to adjust number of
> > queues if they are mapped to hardware queues."
> > More than writing, I even tried to write a skb map by myself,
> Cool and it sounds that you've failed to do so?
Sure, the above precisely explains why it fails to fit in Qdisc context.
Thanks for repeating it.
> At the same time Toke mentioned that he has a prototype of suck skb map.
> What addition data can open your mind that skb/packet map is more
> universal building block for queuing discipline in different layers?
You can add queue at any place you want, what's your problem of
repeating it? What can open your mind to just look at Qdisc?
next prev parent reply other threads:[~2021-09-29 5:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 23:11 [RFC Patch net-next v2] net_sched: introduce eBPF based Qdisc Cong Wang
2021-09-17 18:18 ` Alexei Starovoitov
2021-09-22 3:59 ` Cong Wang
2021-09-22 4:03 ` Alexei Starovoitov
2021-09-22 4:13 ` Cong Wang
2021-09-23 1:49 ` Alexei Starovoitov
2021-09-23 2:05 ` Alexei Starovoitov
2021-09-29 11:47 ` Toke Høiland-Jørgensen
2021-09-29 5:40 ` Cong Wang [this message]
2021-09-29 20:57 ` Alexei Starovoitov
2021-10-01 13:43 ` Jamal Hadi Salim
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).