Re: [PATCH v4 0/10] bql: Byte Queue Limits
From: Dave Taht <hidden>
Date: 2011-11-29 04:23:11
In this test 100 netperf TCP_STREAMs were started to saturate the link. A single instance of a netperf TCP_RR was run with high priority set. Queuing discipline in pfifo_fast, NIC is e1000 with TX ring size set to 1024. tps for the high priority RR is listed. No BQL, tso on: 3000-3200K bytes in queue: 36 tps BQL, tso on: 156-194K bytes in queue, 535 tps
No BQL, tso off: 453-454K bytes int queue, 234 tps BQL, tso off: 66K bytes in queue, 914 tps
Jeeze. Under what circumstances is tso a win? I've always had great trouble with it, as some e1000 cards do it rather badly. I assume these are while running at GigE speeds? What of 100Mbit? 10GigE? (I will duplicate your tests at 100Mbit, but as for 10gigE...) I would suggest TCP_MAERTS as well to saturate the link in the other direction. And then both TCP_STREAM and TCP_MAERTS at the same time while doing RR. -- Dave Täht SKYPE: davetaht US Tel: 1-239-829-5608 FR Tel: 0638645374 http://www.bufferbloat.net