Skip to contentSkip to conversation

New: misleading information about buffer size limits in tcp(7)

Bug 119351 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 2 messages May 31, 2016 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

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/[email protected]
          Reporter: nyh-TS7m/[email protected]
        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".

Signature · 6 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw

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

In reply to a message not in the archive

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

--- Comment #1 from Nadav Har'El <nyh-TS7m/[email protected]> --- 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) :-(

Signature · 6 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html