linux-kernel - Re: seeing strange values for tcp sk_rmem

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: <4B17EF8E.60704@gmail.com>
Date:	Thu, 03 Dec 2009 18:04:14 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Chris Friesen <cfriesen@...tel.com>
CC:	netdev@...r.kernel.org, Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: seeing strange values for tcp sk_rmem_alloc

Chris Friesen a écrit :
> On 12/01/2009 11:52 AM, Eric Dumazet wrote:
> 
>> But be careful of sender tcp stack : It might be delayed a bit,
>> because it waits for receiver to open its window (slow start)
>>
>> You probably need something like
>>
>> while (1) {
>> 	send(fd1, buffer, 2Kbytes);
>> 	sleep(2); // let tcp stack flush its write buffers
>> 	display_sk_rmem_alloc(fd2);
>> }
> 
> Ah, that makes a difference.  But the results (see below) still look
> odd.  For this test, /proc/sys/net/core/rmem_default is 118784.  For
> some reason sk_rmem_alloc gets bumped by 16KB when I only send 2KB of
> data, and it drops back down again every 6 packets.
> 
> Chris

Might be because you use loopback device ? ;)

ifconfig lo | grep MTU
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

After a while (when hitting rcvbuf limit), tcp stack performs skb collapses, to reduce ram usage.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/