From: "Niklas Hambüchen" <mail-7wQd5C9ZzNw@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: net.ipv4.tcp_rmem does override net.core.rmem_max?
Date: Tue, 16 Feb 2016 19:20:17 +0100 [thread overview]
Message-ID: <56C36861.7030904@nh2.me> (raw)
In-Reply-To: <56C356E5.8010004-7wQd5C9ZzNw@public.gmane.org>
Or, there is the following interpretation:
"This value does not override the global
net.core.rmem_max."
might mean
"This value does not override the global
net.core.rmem_max to the extent that it does
not define the upper users can set with SO_RCVBUF.
It does, however, override net.core.rmem_max if
SO_RCVBUF is not used."
This would be consistent with my findings.
I'm not 100% confident about whether this is what the code does though,
see my comment
http://stackoverflow.com/questions/31546835/tcp-receiving-window-size-higher-than-net-core-rmem-max/35438236#comment58576526_35438236
for details on that.
On 16/02/16 18:05, Niklas Hambüchen wrote:
> An answer to the question I just posted,
>
> http://stackoverflow.com/a/35438236/263061
>
> suggests that neither is the case, but in fact the kernel takes the
> maximum of the two values.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-02-16 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 17:04 net.ipv4.tcp_rmem does override net.core.rmem_max? Niklas Hambüchen
[not found] ` <56C35692.7010807-7wQd5C9ZzNw@public.gmane.org>
2016-02-16 17:05 ` Niklas Hambüchen
[not found] ` <56C356E5.8010004-7wQd5C9ZzNw@public.gmane.org>
2016-02-16 18:20 ` Niklas Hambüchen [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=56C36861.7030904@nh2.me \
--to=mail-7wqd5c9zznw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).