BPF List
 help / color / mirror / Atom feed
From: 杨培灏 <yangpeihao@sjtu.edu.cn>
To: sdf@google.com, YrYj3LPaHV7thgJW@google.com
Cc: bpf@vger.kernel.org, cong.wang@bytedance.com, jhs@mojatatu.com,
	jiri@resnulli.us, netdev@vger.kernel.org, toke@redhat.com,
	xiyou.wangcong@gmail.com
Subject: [RFC Patch v5 0/5] net_sched: introduce eBPF based Qdisc
Date: Thu, 22 Sep 2022 15:46:21 +0800 (CST)	[thread overview]
Message-ID: <95092865.3867028.1663832781195.JavaMail.zimbra@sjtu.edu.cn> (raw)

On 06/24, sdf wrote:

> I feel like this patch series (even rfc), should also have a good example
to show that bpf qdisc is on par and can be used to at least implement
existing policies.

I recently build an example for the simplest `pfifo` qdisc based on Cong Wang's patches, 
see https://github.com/Forsworns/sch_bpf/
if you have interests. The sample is a little large, and involving modifications on libbpf, 
so I didn't attach it as a patch here. 

I also run a micro-benchmark with iperf3, see 
https://gist.github.com/Forsworns/71b70ed67d2ac53a4316bac862ce7d0f

I know it's unfair to evaluate the sch_bpf with `pfifo`, since sch_bpf is based on rbtree.
But I think it a good example for other classiful and more complicated qdiscs.
The `pfifo` is simple enough as a start :)

             reply	other threads:[~2022-09-22  8:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  7:46 杨培灏 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-02  4:10 [RFC Patch v5 0/5] net_sched: introduce eBPF based Qdisc Cong Wang
2022-06-24 16:52 ` Toke Høiland-Jørgensen
2022-06-24 17:35   ` Dave Taht
2022-06-24 20:51 ` sdf

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=95092865.3867028.1663832781195.JavaMail.zimbra@sjtu.edu.cn \
    --to=yangpeihao@sjtu.edu.cn \
    --cc=YrYj3LPaHV7thgJW@google.com \
    --cc=bpf@vger.kernel.org \
    --cc=cong.wang@bytedance.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.com \
    --cc=toke@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox