Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1265363
| From | Tom Herbert <tom@herbertland.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: linux-next network throughput performance regression |
| Date | 2015-11-09 06:40 +0100 |
| Message-ID | <qsNlo-2cc-5@gated-at.bofh.it> (permalink) |
| References | <qsKQx-hN-3@gated-at.bofh.it> <qsKQx-hN-1@gated-at.bofh.it> <qsLjz-OT-5@gated-at.bofh.it> <qsLjz-OT-3@gated-at.bofh.it> <qsNlo-2cc-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Nov 8, 2015 at 7:31 PM, Dexuan Cui <decui@microsoft.com> wrote: >> From: David Miller [mailto:davem@davemloft.net] >> Sent: Monday, November 9, 2015 11:24 >> ... >> > Thanks, David! >> > I understand 1 TX queue is the bottleneck (however in Simon's >> > test, TX=1 => 36.7Gb/s, TX=8 => 37.7 Gb/s, so it looks the TX=1 bottleneck >> > is not so obvious). >> > I'm just wondering how the bottleneck became much narrower with >> > recent linux-next in Simon's result (36.7 Gb/s vs. 18.2 Gb/s). IMO there >> > must be some latency somewhere. >> >> I think the whole thing here is that you misinterpreted what Eric said. >> >> He is not arguing that some regression did, or did not, happen. >> >> He instead was making the basic statement about the fact that due to >> the lack of paralellness a single stream TCP case is harder to >> optimize for high speed NICs. >> >> That is all. > Thanks, I got it. > I'm actually new to network performance tuning, trying to understand > all the related details. :-) > You might want to look at https://www.kernel.org/doc/Documentation/networking/scaling.txt as an introduction to the scaling capabilities of the stack. Tom > Thanks, > -- Dexuan > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
linux-next network throughput performance regression Simon Xiao <sixiao@microsoft.com> - 2015-11-06 21:40 +0100
Re: linux-next network throughput performance regression David Ahern <dsa@cumulusnetworks.com> - 2015-11-06 21:50 +0100
Re: linux-next network throughput performance regression David Ahern <dsa@cumulusnetworks.com> - 2015-11-06 22:40 +0100
Re: linux-next network throughput performance regression Eric Dumazet <eric.dumazet@gmail.com> - 2015-11-07 20:40 +0100
Re: linux-next network throughput performance regression Eric Dumazet <eric.dumazet@gmail.com> - 2015-11-07 21:00 +0100
RE: linux-next network throughput performance regression Simon Xiao <sixiao@microsoft.com> - 2015-11-09 21:30 +0100
Re: linux-next network throughput performance regression Eric Dumazet <eric.dumazet@gmail.com> - 2015-11-10 00:10 +0100
Re: linux-next network throughput performance regression David Miller <davem@davemloft.net> - 2015-11-09 04:00 +0100
Re: linux-next network throughput performance regression David Miller <davem@davemloft.net> - 2015-11-09 04:30 +0100
Re: linux-next network throughput performance regression Dave Airlie <airlied@gmail.com> - 2015-11-09 04:40 +0100
Re: linux-next network throughput performance regression Tom Herbert <tom@herbertland.com> - 2015-11-09 06:40 +0100
csiph-web