Slashdot Mirror

← Back to Stories (view on slashdot.org)

Got (Buffer) Bloat?

Posted by Roblimo on from the good-buffering-is-better-than-licking-a-cake-batter-bowl dept.

mtaht writes, "After a very intense month of development, the Bufferbloat project has announced the debloat-testing git kernel tree, featuring (via suggestion of Van Jacobson) a wireless network latency smashing algorithm, (called eBDP), the SFB and CHOKe packet schedulers, and a slew of driver level fixes that reduce network latency across the Linux kernel by over 2 orders of magnitude. Got Bloat?"

1 of 121 comments (clear)

  1. Re:what it is by TheLink · · Score: 4, Insightful

    IMO it's fine for buffers to be very big.

    What routers should do is keep track of how long packets have been in the router (in milliseconds or even microseconds) and use that with QoS stuff (and maybe some heuristics) to figure out which packets to send first, or to drop.

    For example, "bulk/throughput" packets might be kept around for hundreds of milliseconds, but while latency sensitive packets get priority they are dropped if they cannot be sent within tens of milliseconds (then the sender will faster realize that it should slow down).

    --