netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Willem de Bruijn <willemb@google.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH man-pages] man: packet.7: document fanout, ring and auxiliary options
Date: Fri, 06 Dec 2013 20:54:32 +0100	[thread overview]
Message-ID: <52A22B78.8070109@redhat.com> (raw)
In-Reply-To: <1386350329-32723-1-git-send-email-willemb@google.com>

On 12/06/2013 06:18 PM, Willem de Bruijn wrote:
> The packet socket manual page does not list all socket options.
>
> This patch adds descriptions of the common packet socket options
>    PACKET_AUXDATA, PACKET_FANOUT, PACKET_RX_RING, PACKET_STATISTICS,
>    PACKET_TX_RING
>
> and the ring-specific options
>    PACKET_LOSS, PACKET_RESERVE, PACKET_TIMESTAMP, PACKET_VERSION
>
> It does not yet add descriptions for
>    PACKET_COPY_THRESH, PACKET_HDRLEN, PACKET_ORIGDEV,
>    PACKET_TX_HAS_OFF, PACKET_TX_TIMESTAMP, PACKET_VNET_HDR
>
> It tries to balance being informative with exposing kernel detail
> that is unlikely to be used by most readers or that may change
> frequently. For implementation details, the manpage points to the
> documentation in kernel Documentation/networking. Let me know if
> options should be added or removed.
>
> Source: PACKET_FANOUT, PACKET_RX_RING and PACKET_VERSION are in
> /tools/testing/net/psock_fanout.c in the latest Linux kernel source
> tree. PACKET_STATISTICS was in the first version of that test.
> PACKET_TX_RING I have used elsewhere. The other options are based
> on reading kernel code.
>
>   [Very minor fixups. -dborkman]
>
> Signed-off-by: Willem de Bruijn <willemb@google.com>

Acked-by: Daniel Borkmann <dborkman@redhat.com>

I went over the man page again, and it looks good to me.

Great work and thanks for following up Willem!

  reply	other threads:[~2013-12-06 19:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1386081779.git.dborkman@redhat.com>
2013-12-06 10:41 ` [PATCH man-pages] man: packet.7: document fanout, ring and auxiliary options Daniel Borkmann
2013-12-06 16:11   ` Willem de Bruijn
     [not found]     ` <CA+FuTSdCfH_yum57ZWV9tw5cd0=DkWWR-OvnaUEkUf5O7JCQYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-12-06 16:14       ` Daniel Borkmann
     [not found]         ` <52A1F7D7.6040305-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-12-06 17:18           ` Willem de Bruijn
2013-12-06 19:54             ` Daniel Borkmann [this message]
     [not found]               ` <52A22B78.8070109-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-01-04 14:47                 ` Daniel Borkmann
     [not found]                   ` <52C81EF8.6090908-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-01-04 21:57                     ` Michael Kerrisk (man-pages)
     [not found]                       ` <CAKgNAkj8G6VvPLYF56884XcAWw+yOTUcF1UZSRwcYTk52D--zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-04 23:10                         ` Daniel Borkmann

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=52A22B78.8070109@redhat.com \
    --to=dborkman@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    /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).