From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Ophir Munk <ophirmu@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
Moti Haimovsky <motih@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>, Matan Azrad <matan@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: update mlx4 flow limitations
Date: Thu, 8 Feb 2018 18:06:42 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EEAC62D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1518072954-19082-1-git-send-email-ophirmu@mellanox.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ophir Munk
> Sent: Thursday, February 8, 2018 6:56 AM
> To: dev@dpdk.org; Adrien Mazarguil <adrien.mazarguil@6wind.com>; Moti
> Haimovsky <motih@mellanox.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> <olgas@mellanox.com>; Ophir Munk <ophirmu@mellanox.com>; Matan Azrad
> <matan@mellanox.com>
> Subject: [dpdk-dev] [PATCH v1] doc: update mlx4 flow limitations
>
> From: Moti Haimovsky <motih@mellanox.com>
>
> This patch updates mlx4 documentation with flow configuration limitations
> imposed by NIC hardware and PMD implementation
>
> + For example using testpmd command - src mask must be
> + 00:00:00:00:00:00 otherwise the following command will fail
> +
> +.. code-block:: console
> +
> + testpmd> flow create 1 ingress pattern eth
> + src spec 00:16:3e:2b:e6:47 src mask FF:FF:FF:FF:FF:FF
> + / end actions drop / end
Is there a condadiction between "src mask must be 00:00:00:00:00:00"
and the mask used in the example.
Apart from that the doc looks okay.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2018-02-08 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 6:55 Ophir Munk
2018-02-08 18:06 ` Mcnamara, John [this message]
2018-02-09 16:21 ` Adrien Mazarguil
2018-02-09 16:39 ` Thomas Monjalon
2018-02-12 11:23 ` Adrien Mazarguil
2018-02-12 13:58 ` Thomas Monjalon
2018-02-12 14:19 ` Adrien Mazarguil
2018-02-12 16:23 ` Thomas Monjalon
2018-02-11 19:30 ` Marcelo Ricardo Leitner
2018-02-12 7:41 ` Shahaf Shuler
2018-02-12 12:45 ` Marcelo Ricardo Leitner
2018-02-12 13:44 ` Shahaf Shuler
2018-02-24 22:36 ` [dpdk-dev] [PATCH v2] " Ophir Munk
2018-03-13 14:25 ` Adrien Mazarguil
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=B27915DBBA3421428155699D51E4CFE23EEAC62D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=motih@mellanox.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--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).