From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Florian Westphal <fw-HFFVJYpyMKqzQB+pC5nmwQ@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] proc.5: Document /proc/net/netfilter/nfnetlink_queue
Date: Tue, 28 Oct 2014 14:55:57 +0100 [thread overview]
Message-ID: <544FA06D.5070809@gmail.com> (raw)
In-Reply-To: <1413750097-9875-1-git-send-email-fw-HFFVJYpyMKqzQB+pC5nmwQ@public.gmane.org>
Thanks, Florian.
Applied (at last!).
Cheers,
Michael
On 10/19/2014 10:21 PM, Florian Westphal wrote:
> ---
> Changes since v1:
> made a minor edit to better explain the difference between
> 'dropped' and 'user dropped' counters.
>
> man5/proc.5 | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
>
> diff --git a/man5/proc.5 b/man5/proc.5
> index 7ca2226..da4b5b6 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -2770,6 +2770,63 @@ not yet supported in the kernel).
> \&"St" is the internal state of the
> socket and Path is the bound path (if any) of the socket.
> .TP
> +.I /proc/net/netfilter/nfnetlink_queue
> +This file contains information about netfilter userspace queueing, if used.
> +Each line represents a queue. Queues that have not been subscribed to
> +by userspace are not shown.
> +.nf
> +
> + 1 4207 0 2 65535 0 0 0 1
> + (1) (2) (3)(4) (5) (6) (7) (8)
> +.fi
> +.IP
> +The fields in each line are:
> +.RS 7
> +.TP 5
> +(1)
> +The ID of the queue. This matches what is specified in the
> +.B \-\-queue\-num
> +or
> +.B \-\-queue\-balance
> +options to the
> +.BR iptables (8)
> +NFQUEUE target. See
> +.BR iptables-extensions (8)
> +for more information.
> +.TP
> +(2)
> +The netlink port id subscribed to the queue.
> +.TP
> +(3)
> +The number of packets currently queued and waiting to be processed by
> +the application.
> +.TP
> +(4)
> +The copy mode of the queue. It is either 1 (metadata only) or 2
> +(also copy payload data to userspace).
> +.TP
> +(5)
> +Copy range, i.e. how many bytes of packet payload should be copied to
> +userspace at most.
> +.TP
> +(6)
> +queue dropped. Number of packets that had to be dropped by the kernel because
> +too many packets are already waiting for userspace to send back the mandatory
> +accept/drop verdicts.
> +.TP
> +(7)
> +queue user dropped. Number of packets that were dropped within the netlink
> +subsystem. Such drops usually happen when the corresponding socket buffer is
> +full, i.e. userspace is not able to read messages fast enough.
> +.TP
> +(8)
> +sequence number. Every queued packet is associated with a (32-bit)
> +monotonically-increasing sequence number.
> +This shows the ID of the most recent packet queued.
> +.RE
> +.IP
> +The last number only exists for compatibility reasons and is always 1.
> +.TP
> .I /proc/partitions
> Contains the major and minor numbers of each partition as well as the number
> of 1024-byte blocks and the partition name.
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2014-10-28 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 20:21 [PATCH v2] proc.5: Document /proc/net/netfilter/nfnetlink_queue Florian Westphal
[not found] ` <1413750097-9875-1-git-send-email-fw-HFFVJYpyMKqzQB+pC5nmwQ@public.gmane.org>
2014-10-28 13:55 ` Michael Kerrisk (man-pages) [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=544FA06D.5070809@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=fw-HFFVJYpyMKqzQB+pC5nmwQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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).