From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Zhao1, Wei" <wei.zhao1@intel.com>,
TETSURO NAKAMURA <nakamura.tetsuro@lab.ntt.co.jp>,
"Mcnamara, John" <john.mcnamara@intel.com>,
TAKADA Naoki <takada.naoki@lab.ntt.co.jp>,
Satoshi NISHIYAMA <nishiyama.s@lab.ntt.co.jp>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] using rte_flow via tespmd with Intel X552
Date: Tue, 29 Aug 2017 09:26:35 +0200 [thread overview]
Message-ID: <20170829072635.GC4301@6wind.com> (raw)
In-Reply-To: <e666e8d6-3b35-e193-e133-f0dbceb49433@intel.com>
On Tue, Aug 08, 2017 at 09:57:34AM +0100, Ferruh Yigit wrote:
> On 8/2/2017 2:41 PM, Adrien Mazarguil wrote:
> > Hi Wenzhuo,
> >
> > On Wed, Aug 02, 2017 at 01:00:47PM +0000, Lu, Wenzhuo wrote:
> >> Hi,
> >>
> >>> -----Original Message-----
> >>> From: Zhao1, Wei
> >>> Sent: Wednesday, August 2, 2017 3:28 AM
> >>> To: TETSURO NAKAMURA <nakamura.tetsuro@lab.ntt.co.jp>
> >>> Cc: TAKADA Naoki <takada.naoki@lab.ntt.co.jp>; Satoshi NISHIYAMA
> >>> <nishiyama.s@lab.ntt.co.jp>; Lu, Wenzhuo <wenzhuo.lu@intel.com>;
> >>> dev@dpdk.org
> >>> Subject: RE: using rte_flow via tespmd with Intel X552
> >>>
> >>> Hi, NAKAMURA
> >>>
> >>> I have upload 2 documents about command format when creating flow for
> >>> NIC igb and ixgbe in the email attachment.
> >>> I have decided to commit the context in the doc to doc\guides\nics\ixgbe.rst
> >>> before, BUT by now it seems the content of the document is too much To
> >>> store there. So, is there any other doc more suitable in DPDK to record this.
> >>> And welcome for any other suggestion.
> >>> AND, Wenzhuo, what is your opinion for this?
> >> I also have the same feeling that it may make the ixgbe.rst too big.
> >> + John and Adrien. Hi John, Adrien, I'm think about creating a specific doc for rte flow, we can include the examples for every NIC here. Is it good? If so, where's the good place to put it? Thanks.
> >
> > Depends on the kind of examples. Code samples or testpmd flow command?
> > Unless you mean a document that describes individual rte_flow features
> > supported by each NIC?
> >
> > Code samples could be added to a new "Programming flow rules" (or something)
> > section in doc/guide/prog_guide/rte_flow.rst.
> >
> > Another section about NICs could be added in that documentation as well but
> > should only contain a short summary for each of them and a link to the
> > relevant PMD documentation in nics/$PMD.rst (or elsewhere in the DPDK
> > tree), if any.
> >
> > If you want to describe individual rte_flow features supported by each NIC,
> > I think there's no other choice but to create a bunch of
> > doc/guides/nics/features/rte_flow/*.ini files.
>
> Indeed I was thinking doing a change in .ini files related rte flow in 17.11
>
> rte_flow is a method to implement some filtering features, rte_flow
> itself is not a device feature. And filtering features already listed in
> .ini file.
>
> So I was thinking removing rte_flow from feature table, and update
> existing filter features as something like:
> "Ethertype filter = L" --> Feature exist and implemented using Legacy
> method.
> "Ethertype filter = Y" --> Feature exist and implemented using rte flow
>
> Does it make sense?
Yes, I'm fine with that. Detailed information about rte_flow support can be
added later to the relevant PMD documentation if necessary then.
--
Adrien Mazarguil
6WIND
prev parent reply other threads:[~2017-08-29 7:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <725d0083-decc-1427-c0c1-b8c3515aa429@lab.ntt.co.jp>
[not found] ` <42be0cc3-a69b-4e07-be84-41a8deba75cf@lab.ntt.co.jp>
2017-08-02 7:28 ` Zhao1, Wei
2017-08-02 9:02 ` TETSURO NAKAMURA
2017-08-02 9:15 ` Zhao1, Wei
2017-08-02 13:00 ` Lu, Wenzhuo
2017-08-02 13:41 ` Adrien Mazarguil
2017-08-07 8:33 ` Zhao1, Wei
2017-08-08 8:57 ` Ferruh Yigit
2017-08-29 7:26 ` Adrien Mazarguil [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=20170829072635.GC4301@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=nakamura.tetsuro@lab.ntt.co.jp \
--cc=nishiyama.s@lab.ntt.co.jp \
--cc=takada.naoki@lab.ntt.co.jp \
--cc=wei.zhao1@intel.com \
--cc=wenzhuo.lu@intel.com \
/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).