All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Björn Töpel" <bjorn.topel@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Magnus Karlsson <magnus.karlsson@intel.com>,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH] Documentation/networking: fix af_xdp.rst Sphinx warnings
Date: Tue, 21 May 2019 15:23:13 +0200	[thread overview]
Message-ID: <CAJ+HfNjAjCsQViE=t-M6s-d2yN86YYg8c0iO+BVXB9TW42LtuQ@mail.gmail.com> (raw)
In-Reply-To: <ba3ef670-a8ff-abfd-5e86-9b14af626112@infradead.org>

On Mon, 20 May 2019 at 23:23, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix Sphinx warnings in Documentation/networking/af_xdp.rst by
> adding indentation:
>
> Documentation/networking/af_xdp.rst:319: WARNING: Literal block expected; none found.
> Documentation/networking/af_xdp.rst:326: WARNING: Literal block expected; none found.
>
> Fixes: 0f4a9b7d4ecb ("xsk: add FAQ to facilitate for first time users")
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Magnus Karlsson <magnus.karlsson@intel.com>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> ---
>  Documentation/networking/af_xdp.rst |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> --- lnx-52-rc1.orig/Documentation/networking/af_xdp.rst
> +++ lnx-52-rc1/Documentation/networking/af_xdp.rst
> @@ -316,16 +316,16 @@ A: When a netdev of a physical NIC is in
>     all the traffic, you can force the netdev to only have 1 queue, queue
>     id 0, and then bind to queue 0. You can use ethtool to do this::
>
> -   sudo ethtool -L <interface> combined 1
> +     sudo ethtool -L <interface> combined 1
>
>     If you want to only see part of the traffic, you can program the
>     NIC through ethtool to filter out your traffic to a single queue id
>     that you can bind your XDP socket to. Here is one example in which
>     UDP traffic to and from port 4242 are sent to queue 2::
>
> -   sudo ethtool -N <interface> rx-flow-hash udp4 fn
> -   sudo ethtool -N <interface> flow-type udp4 src-port 4242 dst-port \
> -   4242 action 2
> +     sudo ethtool -N <interface> rx-flow-hash udp4 fn
> +     sudo ethtool -N <interface> flow-type udp4 src-port 4242 dst-port \
> +     4242 action 2
>
>     A number of other ways are possible all up to the capabilitites of
>     the NIC you have.
>
>

Acked-by: Björn Töpel <bjorn.topel@intel.com>

  reply	other threads:[~2019-05-21 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 21:22 [PATCH] Documentation/networking: fix af_xdp.rst Sphinx warnings Randy Dunlap
2019-05-21 13:23 ` Björn Töpel [this message]
2019-05-21 14:46 ` 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='CAJ+HfNjAjCsQViE=t-M6s-d2yN86YYg8c0iO+BVXB9TW42LtuQ@mail.gmail.com' \
    --to=bjorn.topel@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.