[Bloat] BQL for vmxnet3 (vmware virtual network driver)
I just suppose this is not possible since it is a virtual driver with no real device attached, right? Given this, codel and fq_codel are not as effective as they could on a VMware guest? Could it eventually be implemented by vmxnet3 querying the host devices? Thanks. ___ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
[Bloat] fixing bufferbloat in 2017
What's left to do? What else can we do? What should we stop doing? What can we do better? -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org ___ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
Re: [Bloat] fixing bufferbloat in 2017
On 22/11/16 16:32, Dave Taht wrote: > What's left to do? Furthering adoption of the code that contains the bloat-related improvements. In my view, the single biggest potential contributor towards driving such adoption would be for Ookla to start measuring and reporting bufferbloat, thereby putting it on the agenda of both end users and carriers (who use Ookla's servers to qualify equipment in their labs). That would in turn put it on the agenda of equipment manufacturers. ___ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
Re: [Bloat] fixing bufferbloat in 2017
On Tue, Nov 22, 2016 at 8:19 AM, Jan Ceuleers wrote: > On 22/11/16 16:32, Dave Taht wrote: >> What's left to do? > > Furthering adoption of the code that contains the bloat-related > improvements. > > In my view, the single biggest potential contributor towards driving > such adoption would be for Ookla to start measuring and reporting > bufferbloat, thereby putting it on the agenda of both end users and > carriers (who use Ookla's servers to qualify equipment in their labs). > That would in turn put it on the agenda of equipment manufacturers. We've been after ookla for years. Samknows, also. The FCC, too. But how to raise awareness further? An open letter? A petition to the white house? A press release? Until then, there's always dslreports and a few other sites. I would like to see the industries most affected by bufferbloat - voip/videoconferencing/gaming,web gain a good recognition of the problem, how to fix it, and who to talk to about it (router makers and ISPs) > ___ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org ___ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
Re: [Bloat] fixing bufferbloat in 2017
On Tue, Nov 22, 2016 at 11:25 AM, Dave Taht wrote: > On Tue, Nov 22, 2016 at 8:19 AM, Jan Ceuleers > wrote: > > On 22/11/16 16:32, Dave Taht wrote: > >> What's left to do? > > > > Furthering adoption of the code that contains the bloat-related > > improvements. > > > > In my view, the single biggest potential contributor towards driving > > such adoption would be for Ookla to start measuring and reporting > > bufferbloat, thereby putting it on the agenda of both end users and > > carriers (who use Ookla's servers to qualify equipment in their labs). > > That would in turn put it on the agenda of equipment manufacturers. > May not matter too much longer... > > We've been after ookla for years. Samknows, also. The FCC, too. But > how to raise awareness further? An open letter? A petition to the > white house? A press release? > > Until then, there's always dslreports and a few other sites. > Comcast has/is funding development of an open source speed test, and the intent is to have a bufferbloat test in it. Several ISP's are on board with it in addition to Comcast and are helping too. You can improve the code... I can dig up the link if someone is hot to trot. Right now, we're discussing how to license the code, however. I don't know what the final outcome of that will be. > > I would like to see the industries most affected by bufferbloat - > voip/videoconferencing/gaming,web gain a good recognition of the > problem, how to fix it, and who to talk to about it (router makers and > ISPs) > Getting cellular manufacturers to understand would also be a good thing, IMHO. - Jim > > > > > ___ > > Bloat mailing list > > Bloat@lists.bufferbloat.net > > https://lists.bufferbloat.net/listinfo/bloat > > > > -- > Dave Täht > Let's go make home routers and wifi faster! With better software! > http://blog.cerowrt.org > ___ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat > ___ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
