From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Simon Xu <xu.simon@oracle.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] sctp: enlarge SO_RCVBUF option value
Date: Mon, 04 Nov 2013 16:25:24 +0800 [thread overview]
Message-ID: <527759F4.8040606@cn.fujitsu.com> (raw)
In-Reply-To: <1383542895-14069-1-git-send-email-xu.simon@oracle.com>
On 11/04/2013 01:28 PM, Simon Xu wrote:
> When using setsockopt() with recent Linux kernels, it doesn't make sense to
> use a value smaller than SOCK_MIN_RCVBUF/2 for SO_RCVBUF and expect getting
> a SO_RCVBUF value by getsockopt() which is doubled. See the following code
> in linux/net/core/sock.c:
>
> if ((val * 2) < SOCK_MIN_RCVBUF)
> sk->sk_rcvbuf = SOCK_MIN_RCVBUF;
> else
> sk->sk_rcvbuf = val * 2;
> break;
>
> SOCK_MIN_RCVBUF is defined as (2048 + sizeof(struct sk_buff)) which is 2240.
> ---
> testcases/network/sctp/func_tests/test_1_to_1_sockopt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Applied, thank you. Please add your Signed-off-by next time as Jan pointed out.
Wanlong Gao
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-11-04 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 5:28 [LTP] [PATCH] sctp: enlarge SO_RCVBUF option value Simon Xu
2013-11-04 8:18 ` Jan Stancek
2013-11-04 8:25 ` Wanlong Gao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=527759F4.8040606@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=xu.simon@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox