linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Andrich <carsten.andrich-hs6bpBdVsEZfm0AUMx9V0g@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Daniel Borkmann
	<dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Willem de Bruijn
	<willemb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
	Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	Michael Kerrisk-manpages
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Improving PACKET_{RX,TX}_RING documentation
Date: Sat, 17 May 2014 15:13:26 +0200	[thread overview]
Message-ID: <1400332406.2395.35.camel@actium.fritz.box> (raw)

Hello again everyone,

roughly 3 weeks ago the aftermath of an actually minor patch to fix an
inaccuracy in packet.7's PACKET_TX_RING-related documentation led me to
offer improving the entire PACKET_{RX,TX}_RING-documentation.
Since I do happen to have most of my spare time back by now, I'd like to
tackle this effort before I change my mind :)

On 04/24/2014 12:21 PM, Michael Kerrisk (man-pages) wrote:
> I'd leave that plan largely to you. It sounds like Willem and
> Daniel are willing to help out.

I'd like to start with getting packet.7's documentation of
PACKET_{RX,TX}_RING into a shape, that should allow most readers to
actually use it without consulting packet_mmap.txt. The latter can be
quite confusing for those unfamiliar with PACKET_{RX,TX}_RING.

I plan to do the following to packet.7:
     1. Increase detail of PACKET_{RX,TX}_RING socket options, including
        description of struct tpacket_hdr and anything else required to
        operate the ring.
     2. Move some details from other sockopts (e.g. PACKET_LOSS) into
        *_RING.
     3. Add fully functional example source code for simple
        PACKET_{RX,TX}_RING operation (initialization and operation).
        This may be as much as 3 different example programs if I
        incorporate [2] and [3] in an appropriate manner. It might be a
        good idea to add a non-*_RING example as well.
     4. Add a warning about inferior _TX_RING performance [1] which I
        suffered from only recently in the measurements I made for my
        thesis on Linux 3.14.
     5. Other minor changes that'll come up while taking care of 1 thru
        4 :)

Any suggestions regarding this rough course of action?

Cheers,
Carsten

[1]https://github.com/netsniff-ng/netsniff-ng/commit/c3602a9
[2]https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/networking/packet_mmap.txt?id=66e56cd46b93ef407c60adcac62cf33b06119d50
[3]https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Documentation/networking/packet_mmap.txt?id=7e11daa7c19ec319fa4b750fd249a18957f17797

--
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

             reply	other threads:[~2014-05-17 13:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17 13:13 Carsten Andrich [this message]
     [not found] ` <1400332406.2395.35.camel-FQO4gtnRtnzkVFMGpb/cPg@public.gmane.org>
2014-05-19  4:54   ` Improving PACKET_{RX,TX}_RING documentation Michael Kerrisk (man-pages)
     [not found]     ` <53798E97.1000505-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-19 10:14       ` Daniel Borkmann
     [not found]         ` <5379D9A2.1070008-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-19 15:05           ` Willem de Bruijn
     [not found]             ` <CA+FuTSeWh_iQGqc-4usL7vr28OrkHTnBvHvXvVO=LcGsNRgtMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-19 16:01               ` Daniel Borkmann
2014-05-22 12:22               ` Carsten Andrich
2014-05-22 13:13                 ` Michael Kerrisk (man-pages)
2014-05-22 13:37                 ` Jesper Dangaard Brouer
2014-05-22 14:51                 ` Willem de Bruijn
     [not found]                   ` <CA+FuTSfpORKtm_kdG+CycoPiq+Gxf58=nXqKApFEmR+xZs69_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-26 10:49                     ` Carsten Andrich

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=1400332406.2395.35.camel@actium.fritz.box \
    --to=carsten.andrich-hs6bpbdvsezfm0aumx9v0g@public.gmane.org \
    --cc=dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=willemb-hpIqsD4AKlfQT0dZR+AlfA@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).