From: Pascal Mazon <pascal.mazon@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add Linux flower support check in TAP guide
Date: Wed, 20 Sep 2017 15:08:52 +0200 [thread overview]
Message-ID: <a5dcfb4b-bac5-458d-d439-f7db1593130c@6wind.com> (raw)
In-Reply-To: <20170920130313.28068-1-thomas@monjalon.net>
Acked-by: Pascal Mazon <pascal.mazon@6wind.com>
On 20/09/2017 15:03, Thomas Monjalon wrote:
> The flow API is supported in TAP PMD if flower is supported in Linux.
> Some commands are combined to suggest a convenient check of its support
> by the running kernel.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> doc/guides/nics/tap.rst | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/nics/tap.rst b/doc/guides/nics/tap.rst
> index f3ee95d28..04086b110 100644
> --- a/doc/guides/nics/tap.rst
> +++ b/doc/guides/nics/tap.rst
> @@ -113,7 +113,14 @@ Flow API support
> ----------------
>
> The tap PMD supports major flow API pattern items and actions, when running on
> -linux kernels above 4.2 ("Flower" classifier required). Supported items:
> +linux kernels above 4.2 ("Flower" classifier required).
> +The kernel support can be checked with this command::
> +
> + zcat /proc/config.gz | ( grep 'CLS_FLOWER=' || echo 'not supported' ) |
> + tee -a /dev/stderr | grep -q '=m' &&
> + lsmod | ( grep cls_flower || echo 'try modprobe cls_flower' )
> +
> +Supported items:
>
> - eth: src and dst (with variable masks), and eth_type (0xffff mask).
> - vlan: vid, pcp, tpid, but not eid. (requires kernel 4.9)
next prev parent reply other threads:[~2017-09-20 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 13:03 Thomas Monjalon
2017-09-20 13:08 ` Pascal Mazon [this message]
2017-09-25 11:23 ` Mcnamara, John
2017-09-25 13:00 ` Ferruh Yigit
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=a5dcfb4b-bac5-458d-d439-f7db1593130c@6wind.com \
--to=pascal.mazon@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).