| 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
| ||
|
Date: Tue, 3 Aug 2010 18:48:29 -0600 From: Jack Zhang <jack.zhang2011@...il.com> To: Rick Jones <rick.jones2@...com> Cc: netdev@...r.kernel.org Subject: Re: can TCP socket send buffer be over used? Hi Rick, Thanks for your reply. Do you maybe know which part of the source code implements the details about how much send buffer can actually be used for the data payload? Thanks a lot! Jack On 3 August 2010 18:30, Rick Jones <rick.jones2@...com> wrote: > Jack Zhang wrote: >> >> I understand that when the buffer size is set to 128 KB, I actually >> got a buffer of 256 KB as the kernel doubles the buffer size. I also >> understand that half the doubled buffer size is used for meta data >> instead of the actual data to be transferred. So basically the >> effective buffer sizes for the two examples are just 128 KB and 512 >> KB respectively. > > It may not be strictly 1/2. One way to check would be to take a tcpdump > trace on the sending side, and either work-out manually the most the > connection has outstanding at a time, or run the binary trace through > something like tcptrace. > > rick jones > -- 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
Powered by blists - more mailing lists