Hello!
> 1) setsockopt(SO_SNDBUF,x);
> y=getsockopt(SO_SNDBUF);
>
> now y=2*x
Probably. Though I do not think that it is a problem.
At least because it was not a problem until now 8)
Note, that function SO_SNDBUF -> sk->sndbuf is not 1-1 mapping in any case.
F.e. do setsockopt(SO_SNDBUF, 10000000);
Look, what getsockopt(SO_SNDBUF) returns after this.
> 2) or
> x = get_wmem_default_with_sysctl();
> setsockopt(SO_SNDBUF,x);
Why did you decide that this is valid sequence?
wmem_default is not a value to feed to setsockopt().
If it were, it would be called sndbuf_default.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:17 EST