From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org
Subject: Re: [PATCH net-next] docs: nf_flowtable: fix compilation and warnings
Date: Fri, 26 Mar 2021 12:04:09 +1100 [thread overview]
Message-ID: <20210326120354.622089e9@elm.ozlabs.ibm.com> (raw)
In-Reply-To: <20210325211018.5548-1-pablo@netfilter.org>
[-- Attachment #1: Type: text/plain, Size: 2476 bytes --]
Hi Pablo,
On Thu, 25 Mar 2021 22:10:16 +0100 Pablo Neira Ayuso <pablo@netfilter.org> wrote:
>
> ... cannot be used in block quote, it breaks compilation, remove it.
>
> Fix warnings due to missing blank line such as:
>
> net-next/Documentation/networking/nf_flowtable.rst:142: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> Fixes: 143490cde566 ("docs: nf_flowtable: update documentation with enhancements")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> Documentation/networking/nf_flowtable.rst | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/networking/nf_flowtable.rst b/Documentation/networking/nf_flowtable.rst
> index d87f253b9d39..d757c21c10f2 100644
> --- a/Documentation/networking/nf_flowtable.rst
> +++ b/Documentation/networking/nf_flowtable.rst
> @@ -112,6 +112,7 @@ You can identify offloaded flows through the [OFFLOAD] tag when listing your
> connection tracking table.
>
> ::
> +
> # conntrack -L
> tcp 6 src=10.141.10.2 dst=192.168.10.2 sport=52728 dport=5201 src=192.168.10.2 dst=192.168.10.1 sport=5201 dport=52728 [OFFLOAD] mark=0 use=2
>
> @@ -138,6 +139,7 @@ allows the flowtable to define a fastpath bypass between the bridge ports
> device (represented as eth0) in your switch/router.
>
> ::
> +
> fastpath bypass
> .-------------------------.
> / \
> @@ -168,12 +170,12 @@ connection tracking entry by specifying the counter statement in your flowtable
> definition, e.g.
>
> ::
> +
> table inet x {
> flowtable f {
> hook ingress priority 0; devices = { eth0, eth1 };
> counter
> }
> - ...
> }
>
> Counter support is available since Linux kernel 5.7.
> @@ -185,12 +187,12 @@ If your network device provides hardware offload support, you can turn it on by
> means of the 'offload' flag in your flowtable definition, e.g.
>
> ::
> +
> table inet x {
> flowtable f {
> hook ingress priority 0; devices = { eth0, eth1 };
> flags offload;
> }
> - ...
> }
>
> There is a workqueue that adds the flows to the hardware. Note that a few
Thanks.
I will add this into linux-next today and will drop it when it (or
something similar) turns up in a tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-26 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 21:10 [PATCH net-next] docs: nf_flowtable: fix compilation and warnings Pablo Neira Ayuso
2021-03-26 1:04 ` Stephen Rothwell [this message]
2021-03-26 21:50 ` patchwork-bot+netdevbpf
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=20210326120354.622089e9@elm.ozlabs.ibm.com \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).