From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>, linux-man@vger.kernel.org
Cc: mtk.manpages@gmail.com, andi@firstfloor.org, netdev@vger.kernel.org
Subject: Re: [PATCH] af_packet: Add PACKET_FANOUT_QM documentation
Date: Sat, 22 Feb 2014 10:44:40 +0100 [thread overview]
Message-ID: <53087188.9080408@gmail.com> (raw)
In-Reply-To: <1390911375-5784-1-git-send-email-nhorman@tuxdriver.com>
On 01/28/2014 01:16 PM, Neil Horman wrote:
> Recently added a new fanout mode of operation to packet sockets. Document it
> here
Thanks, Neil. Applied.
This new mode is ne win 3.14, right?
Cheers,
Michael
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> CC: mtk.manpages@gmail.com
> CC: andi@firstfloor.org
> CC: netdev@vger.kernel.org
> ---
> man7/packet.7 | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/man7/packet.7 b/man7/packet.7
> index 93f91e9..6e145dc 100644
> --- a/man7/packet.7
> +++ b/man7/packet.7
> @@ -296,6 +296,8 @@ processes all data on a single socket, moves to the next when one
> becomes backlogged.
> .BR PACKET_FANOUT_RND
> selects the socket using a pseudo-random number generator.
> +.BR PACKET_FANOUT_QM
> +selects the socket using the recorded queue_mapping of the received skb.
>
> Fanout modes can take additional options.
> IP fragmentation causes packets from the same flow to have different
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2014-02-22 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 12:16 [PATCH] af_packet: Add PACKET_FANOUT_QM documentation Neil Horman
2014-02-22 9:44 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <53087188.9080408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-22 12:35 ` Daniel Borkmann
[not found] ` <5308998F.50907-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-02-23 7:27 ` Michael Kerrisk (man-pages)
2014-02-23 22:23 ` Neil Horman
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=53087188.9080408@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-man@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).