[Bug 119351] New: misleading information about buffer size limits in tcp(7)

[Bug 119351] New: misleading information about buffer size limits in tcp(7)

[bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r]

https://bugzilla.kernel.org/show_bug.cgi?id=119351

            Bug ID: 119351
           Summary: misleading information about buffer size limits in
                    tcp(7)
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
          Reporter: nyh-TS7m/3hpY0sOpacJJkBjfT4kX+cae0hd@public.gmane.org
        Regression: No

The tcp(7) discussion on SO_SNDBUF and SO_RCVBUF contains the statement that:
"The maximum sizes for socket buffers declared  via  the  SO_SNDBUF  and
SO_RCVBUF    mechanisms    are   limited   by   the   values   in   the      
/proc/sys/net/core/rmem_max  and   /proc/sys/net/core/wmem_max   files."

However, other sources seem to suggest that the files
/proc/sys/net/ipv4/tcp_wmem and /proc/sys/net/ipv4/tcp_rmem (mentioned in the
previous paragraph) actually contain the relevant limits (the third value in
each file), while the core/ files are only relevant to other protocols. This is
actually explained in tcp(7), down in the "tcp_rmem" section of the "/proc
interfaces".

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
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

[Bug 119351] misleading information about buffer size limits in tcp(7)

[bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r]

https://bugzilla.kernel.org/show_bug.cgi?id=119351

--- Comment #1 from Nadav Har'El <nyh-TS7m/3hpY0sOpacJJkBjfT4kX+cae0hd@public.gmane.org> ---
Hmm, reading the text again, the tcp_rmem section actually states that: "This
value does not override  the  global net.core.rmem_max.". It's not clear what
this actually means: Does it mean tcp_rmem maximum is just ignored? That it
cannot *increase* core.rmem_max? Or what?

This whole topic is really unclear in tcp(7) :-(

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
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