On Thu, Feb 27, 2014 at 6:08 PM, clanlab.proj <clanlab.proj@xxxxxxxxx> wrote: > On Thu, Feb 27, 2014 at 5:25 PM, clanlab.proj <clanlab.proj@xxxxxxxxx> wrote: > >> Hi all, >> After I've replaced the WEIGHT/budget from 16 -> 32, >> I've got better performance from previous NAPI version, but still >> cannot beat the work queue version. Dear all, Update a benchmark of single tcp RX session comparison. I've tested NAPI implementation with (budget) WEIGHT = 8, 16, 32. and work queue implementation. The picture below is the analysis result by wireshark to present a visualization. http://i.imgur.com/wluSt4f.png Compared with the iperf log and wireshark statistic result, you can see the work queue method gets the best result among the other tests includes the maximum throughput and minimum throughput. If you compared the result of budget change, you can see when WEIGHT = 8, you will get the most smooth throughput but it cannot reach the maximum result of all NAPI method. I have not test the others scenarios, for example, to compare the difference of multiple sessions or bi-directional traffics. But I think I won't do these test. According to the testing result right now, I'll suggest work queue method instead of NAPI implementation. Best regards, Weinn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
