From: Pedro Tammela <pctammela@mojatatu.com>
To: netdev@vger.kernel.org
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, shaozhengchao@huawei.com,
victor@mojatatu.com, simon.horman@corigine.com,
paolo.valente@unimore.it, Pedro Tammela <pctammela@mojatatu.com>
Subject: [PATCH net v3 0/4] net/sched: fixes for sch_qfq
Date: Tue, 11 Jul 2023 18:00:59 -0300 [thread overview]
Message-ID: <20230711210103.597831-1-pctammela@mojatatu.com> (raw)
Patch 1 fixes a regression introduced in 6.4 where the MTU size could be
bigger than 'lmax'.
Patch 3 fixes an issue where the code doesn't account for qdisc_pkt_len()
returning a size bigger then 'lmax'.
Patches 2 and 4 are selftests for the issues above.
v2 -> v3:
- Added Eric tags
- Addressed issue in patch 4 pointed by Shaozheng
v1 -> v2:
- Added another fix and selftest for sch_qfq
- Addressed comment by Simon
- Added Jamal acks and Shaozheng tested by
Pedro Tammela (4):
net/sched: sch_qfq: reintroduce lmax bound check for MTU
selftests: tc-testing: add tests for qfq mtu sanity check
net/sched: sch_qfq: account for stab overhead in qfq_enqueue
selftests: tc-testing: add test for qfq with stab overhead
net/sched/sch_qfq.c | 18 +++-
.../tc-testing/tc-tests/qdiscs/qfq.json | 86 +++++++++++++++++++
2 files changed, 101 insertions(+), 3 deletions(-)
--
2.39.2
next reply other threads:[~2023-07-11 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 21:00 Pedro Tammela [this message]
2023-07-11 21:01 ` [PATCH net v3 1/4] net/sched: sch_qfq: reintroduce lmax bound check for MTU Pedro Tammela
2023-07-13 8:31 ` Simon Horman
2023-07-11 21:01 ` [PATCH net v3 2/4] selftests: tc-testing: add tests for qfq mtu sanity check Pedro Tammela
2023-07-13 8:33 ` Simon Horman
2023-07-13 9:01 ` shaozhengchao
2023-07-11 21:01 ` [PATCH net v3 3/4] net/sched: sch_qfq: account for stab overhead in qfq_enqueue Pedro Tammela
2023-07-13 8:35 ` Simon Horman
2023-07-13 8:56 ` Paolo Abeni
2023-07-11 21:01 ` [PATCH net v3 4/4] selftests: tc-testing: add test for qfq with stab overhead Pedro Tammela
2023-07-13 8:36 ` Simon Horman
2023-07-13 9:05 ` shaozhengchao
2023-07-13 9:50 ` [PATCH net v3 0/4] net/sched: fixes for sch_qfq patchwork-bot+netdevbpf
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=20230711210103.597831-1-pctammela@mojatatu.com \
--to=pctammela@mojatatu.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paolo.valente@unimore.it \
--cc=shaozhengchao@huawei.com \
--cc=shuah@kernel.org \
--cc=simon.horman@corigine.com \
--cc=victor@mojatatu.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.