Hi Ben, Ben Hutchings <b...@decadent.org.uk> (03/08/2012): > Byte queue limits (BQL) are an important step in reducing 'bufferbloat' > and network latency on Linux. The feature was introduced in Linux 3.3 > and has had a few bug fixes since then; I think it can be considered > stable now. It requires specific support in drivers and is then > unconditionally enabled for them. It provides some tuning parameters, > but should not normally require these to be changed.
thanks for the background. > I have prepared a backport of this to Linux 3.2 that I would like to > include in wheezy, but I ran out of time to do that before the freeze. > Since BQL is a new feature, it would not normally be allowed to make such > a change now. However, it may also be considered an important fix for > performance problems (high network latency). Therefore I am requesting a > freeze exception in category 5, "pre-approved fixes". I believe it can > be easily backed-out in case it causes regressions. That looks good to me. > BQL requires an ABI change, but so do some of the fixes in Linux 3.2.25, > so the next upload will have an ABI bump in any case. [ Hijacking the subject a bit, adding -boot@ ] That's one of the things I wanted to spend a little time on, while getting back to the block-udeb-ified packages. Now that d-i wheezy beta1 is finally out, I'll try and figure out what exactly breaks in d-i when the linux kernelgets its ABI bumped. Apparently netboot and mini.iso are concerned, but it would be nice to have that checked, and documented. Maybe we could just have a way to prevent some udebs from being decrufted? Now, for other images, maybe we should just perform a debian-installer upload, tweaking the linux ABI bits, each time we let a new linux ABI into testing. Getting that debian-installer into testing would ensure weekly builds work properly, even if no {alpha,beta,rc} are planned when that migration happens. Mraw, KiBi.
signature.asc
Description: Digital signature