From: Daniel Borkmann <dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
brouer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH man-page] packet.7: document PACKET_QDISC_BYPASS
Date: Tue, 28 Jan 2014 15:26:39 +0100 [thread overview]
Message-ID: <52E7BE1F.50206@redhat.com> (raw)
In-Reply-To: <52E7BDAD.7010005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 01/28/2014 03:24 PM, Michael Kerrisk (man-pages) wrote:
> Daniel,
>
> I've applied this patch. I have a question below.
>
> On 12/10/2013 04:31 PM, Daniel Borkmann wrote:
>> Add a comment about PACKET_QDISC_BYPASS' socket option to the kernel.
>>
>> Signed-off-by: Daniel Borkmann <dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>> ---
>> Michael, this patch is on top of Willem's resend for packet.7:
>> http://www.spinics.net/lists/linux-man/msg04576.html
>>
>> Kernel part of this man page update:
>> https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=d346a3fae3ff1d99f5d0c819bf86edf9094a26a1
>>
>> Thanks!
>>
>> man7/packet.7 | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/man7/packet.7 b/man7/packet.7
>> index e0993d2..100f876 100644
>> --- a/man7/packet.7
>> +++ b/man7/packet.7
>> @@ -426,6 +426,11 @@ creates a packet receive ring of variant
>> .BR TPACKET_V1 .
>> To create another variant, configure the desired variant by setting this
>> integer option before creating the ring.
>> +.TP
>> +.BR PACKET_QDISC_BYPASS " (since Linux 3.14)"
>> +By default, packets sent through packet sockets pass through the kernel's
>> +qdisc (traffic control) layer. This can be bypassed by setting this integer
>> +option to one for usage scenarios similar to pktgen.
>
> This last sentence is a little unclear. Would it be better as:
>
> This can be bypassed by setting this integer
> option to one; this is useful for usage scenarios similar to pktgen.
Yes, sounds good to me, thanks Michael.
> Or something like that. Also, can you elaborate a little on what
> pktgen is please.
>
> Thanks,
>
> Michael
>
>
>
>> .SS Ioctls
>> .B SIOCGSTAMP
>>
>
>
--
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-01-28 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:31 [PATCH man-page] packet.7: document PACKET_QDISC_BYPASS Daniel Borkmann
[not found] ` <1386689485-18833-1-git-send-email-dborkman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-01-07 23:34 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkiW5hnYZqUYQv_mWeGyVNgN+Edu5uViX2PxVwhrrGnOQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-07 23:37 ` Daniel Borkmann
2014-01-26 13:30 ` Daniel Borkmann
2014-01-28 14:24 ` Michael Kerrisk (man-pages)
[not found] ` <52E7BDAD.7010005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-01-28 14:26 ` Daniel Borkmann [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=52E7BE1F.50206@redhat.com \
--to=dborkman-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=brouer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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).