From: Cyril Hrubis <chrubis@suse.cz>
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] sctp/test_1_to_1_sockopt.c: set SO_SNDBUF above the defined minimum
Date: Wed, 11 Mar 2015 11:30:11 +0100 [thread overview]
Message-ID: <20150311103011.GA3713@rei> (raw)
In-Reply-To: <1425986309-12966-1-git-send-email-alexey.kodanev@oracle.com>
Hi!
> SO_SNDBUF have the following minimum value:
> TCP_SKB_MIN_TRUESIZE (2048 + sizeof(struct sk_buff))
> SOCK_MIN_SNDBUF (TCP_SKB_MIN_TRUESIZE * 2)
>
> The test set 'SO_SNDBUF' to 2048, then it gets the value back
> with getsockopt(). But the value was defaulted in the kernel
> to the SOCK_MIN_SNDBUF.
I guess that the setsockopt() does that without failing and then
the comparsion of the value you get with getsockopt() fails, right?
I still do not get why the code does:
if ((2 * sndbuf_val_set) != sndbuf_val_get)
Shouldn't the sndbuf_val_set == sndbuf_val_get once the value is changed
to 5000?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2015-03-11 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 11:18 [LTP] [PATCH] sctp/test_1_to_1_sockopt.c: set SO_SNDBUF above the defined minimum Alexey Kodanev
2015-03-11 10:30 ` Cyril Hrubis [this message]
[not found] ` <55002A64.6040108@oracle.com>
2015-03-11 11:48 ` Cyril Hrubis
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=20150311103011.GA3713@rei \
--to=chrubis@suse.cz \
--cc=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vasily.isaenko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.