From: Neil Horman <nhorman@tuxdriver.com>
To: linux-man@vger.kernel.org
Cc: Neil Horman <nhorman@tuxdriver.com>,
mtk.manpages@gmail.com, andi@firstfloor.org,
netdev@vger.kernel.org
Subject: [PATCH] socket: Add SO_RXQ_OVFL documentation
Date: Tue, 28 Jan 2014 07:24:37 -0500 [thread overview]
Message-ID: <1390911877-5984-1-git-send-email-nhorman@tuxdriver.com> (raw)
Add documentation for the SO_RXQ_OVFL socket option
Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
CC: mtk.manpages@gmail.com
CC: andi@firstfloor.org
CC: netdev@vger.kernel.org
---
man7/socket.7 | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/man7/socket.7 b/man7/socket.7
index 6b229dd..aa0aad9 100644
--- a/man7/socket.7
+++ b/man7/socket.7
@@ -663,6 +663,11 @@ with a specific port then it is not possible
to bind to this port for any local address.
Argument is an integer boolean flag.
.TP
+.B SO_RXQ_OVFL
+Indicates that an unsigned 32 bit value ancilliary msg (cmsg) should be attached
+to recieved skbs indicating the number of packets dropped by the socket between
+the last recieved packet and this received packet
+.TP
.B SO_SNDBUF
Sets or gets the maximum socket send buffer in bytes.
The kernel doubles this value (to allow space for bookkeeping overhead)
--
1.8.3.1
next reply other threads:[~2014-01-28 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 12:24 Neil Horman [this message]
[not found] ` <1390911877-5984-1-git-send-email-nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-02-22 9:36 ` [PATCH] socket: Add SO_RXQ_OVFL documentation Michael Kerrisk (man-pages)
[not found] ` <53086F88.5040209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-22 16:22 ` Andi Kleen
[not found] ` <20140222162253.GJ22728-1g7Xle2YJi4/4alezvVtWx2eb7JE58TQ@public.gmane.org>
2014-02-23 7:51 ` Michael Kerrisk (man-pages)
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=1390911877-5984-1-git-send-email-nhorman@tuxdriver.com \
--to=nhorman@tuxdriver.com \
--cc=andi@firstfloor.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.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).