From: Junjie Cao <junjie.cao@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, jhs@mojatatu.com,
jiri@resnulli.us, vinicius.gomes@intel.com, shuah@kernel.org,
bestswngs@gmail.com, uladzislau.zhauniarovich@gmail.com,
hdanton@sina.com,
syzbot+19d01f6082ec61dd45b2@syzkaller.appspotmail.com,
syzbot+8785aaf121cfb2141e0d@syzkaller.appspotmail.com,
syzbot+2642f347f7309b4880dc@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v2 2/3] net/sched: taprio: enforce a minimum interval for software schedules
Date: Mon, 31 Aug 2026 15:30:46 +0800 [thread overview]
Message-ID: <20260831073046.409848-1-junjie.cao@intel.com> (raw)
In-Reply-To: <20260824185337.2704003-1-kuba@kernel.org>
On Mon, 24 Aug 2026 11:53:37 -0700, Jakub Kicinski <kuba@kernel.org> wrote:
> Since the change carries a Fixes: tag it will be picked up for stable, so
> working 802.1Qbv configurations would stop loading after a stable update.
Dropped in v3. With 1/3 fixed, an interval below the expiry cost only
burns CPU on bounded back-to-back expiries, and syzbot already confirmed
1/3 alone on a fourth bucket (link in my 1/3 reply). I'll re-test the
other three the same way before v3.
> Was flooring the rearm interval at runtime in advance_sched() considered as
[...]
Yes, [1] in the cover letter. On top of 1/3 it would only cap the expiry
rate for schedules already below the service cost, with one more
constant to pick. Can do as a follow-up if you want that.
next prev parent reply other threads:[~2026-08-31 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 6:27 [PATCH net v2 0/3] net/sched: taprio: fix software schedule livelocks Junjie Cao
2026-08-20 6:27 ` [PATCH net v2 1/3] net/sched: taprio: catch up in bounded time when the schedule falls behind Junjie Cao
2026-08-24 18:53 ` Jakub Kicinski
2026-08-31 7:30 ` Junjie Cao
2026-08-20 6:27 ` [PATCH net v2 2/3] net/sched: taprio: enforce a minimum interval for software schedules Junjie Cao
2026-08-24 18:53 ` Jakub Kicinski
2026-08-31 7:30 ` Junjie Cao [this message]
2026-08-20 6:27 ` [PATCH net v2 3/3] selftests/tc-testing: taprio: add case for the software minimum interval Junjie Cao
2026-08-24 18:53 ` Jakub Kicinski
2026-08-31 7:31 ` Junjie Cao
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=20260831073046.409848-1-junjie.cao@intel.com \
--to=junjie.cao@intel.com \
--cc=bestswngs@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=syzbot+19d01f6082ec61dd45b2@syzkaller.appspotmail.com \
--cc=syzbot+2642f347f7309b4880dc@syzkaller.appspotmail.com \
--cc=syzbot+8785aaf121cfb2141e0d@syzkaller.appspotmail.com \
--cc=uladzislau.zhauniarovich@gmail.com \
--cc=vinicius.gomes@intel.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.