On Mon, 24 Aug 2026 11:53:37 -0700, Jakub Kicinski <[email protected]> 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.
