Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for June 20, 2013
Pencil, Pencil, and Pencil
Dividing the Linux desktop
LWN.net Weekly Edition for June 13, 2013
A report from pgCon 2013
I wonder if it's a similar cause.
Thanks for the details Jonathan!
prefetch and buffer bloat
Posted May 24, 2011 16:22 UTC (Tue) by martinfick (subscriber, #4455)
Posted May 24, 2011 16:50 UTC (Tue) by nye (guest, #51576)
Posted May 24, 2011 17:11 UTC (Tue) by martinfick (subscriber, #4455)
Posted Jun 2, 2011 21:54 UTC (Thu) by jch (guest, #51929)
Bufferbloat is not about reducing the amount of buffers in routers; it is about designing algorithms to make sure that routers only use as much of their buffers as necessary, and getting the router vendors to deploy such algorithms.
Posted May 24, 2011 17:27 UTC (Tue) by nicooo (guest, #69134)
Posted May 24, 2011 22:58 UTC (Tue) by Lennie (subscriber, #49641)
So again you have manufactures doing non-real-world test (which might have been a good test a long time ago) for marketing purposes and optimising for that case.
Posted May 31, 2011 20:43 UTC (Tue) by marcH (subscriber, #57642)
... up to a size after which throughput does not get better. Yet we can sometimes see buffer sizes way past this point (e.g. 1 second), which proves that some manufacturers do not bother trying to optimize anything at all.
Posted May 31, 2011 21:05 UTC (Tue) by dlang (✭ supporter ✭, #313)
since they have the ram anyway, and buffers that are too small can cause problems. the logic then follows 'why not just use the ram in the device as a buffer'
this causes other problems, but these other problems were not well described until recently.
Posted May 24, 2011 17:53 UTC (Tue) by clugstj (subscriber, #4020)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds