netdev - Re: can TCP socket send buffer be over used?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikJvTvzuPhJ59RNcCGXPWP4EidaHx0=oUK8jjiy@mail.gmail.com>
Date:	Wed, 4 Aug 2010 02:03:45 -0600
From:	Jack Zhang <jack.zhang2011@...il.com>
To:	Mikael Abrahamsson <swmike@....pp.se>
Cc:	netdev@...r.kernel.org
Subject: Re: can TCP socket send buffer be over used?

Hi Mikael,

Thanks for your reply. I'll definitely try that.

Quick question though... the link I use in my test does not have any
packet loss (it's a straight through cable between two PCs)... in this
case, would TCP congestion window size affect the result at all?

Thanks,
Jack

On 4 August 2010 01:33, Mikael Abrahamsson <swmike@....pp.se> wrote:
> On Tue, 3 Aug 2010, Jack Zhang wrote:
>
>> For example, when I set the send buffer size to 128 KB, i could get a
>> throughput up to 43 Mbps, which seems to be impossible as the (buffer
>> size) / RTT is only 10 Mbps.
>
> Are you sure the buffer actually corresponds to the congestion window TCP
> uses? I think you should use wireshark to dump the traffic and look in the
> TCP headers of the packets to see what is actually going on on the wire.
>
> --
> Mikael Abrahamsson    email: swmike@....pp.se
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html