DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: 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: Mon, 7 Aug 2017 08:33:43 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07C45503@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <20170802134108.GX19852@6wind.com>

Hi, Adrien

> -----Original Message-----
> From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com]
> Sent: Wednesday, August 2, 2017 9:41 PM
> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Cc: 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
> Subject: Re: using rte_flow via tespmd with Intel X552
> 
> 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.

Your suggestion of create a bunch under > doc/guides/nics/features/rte_flow/*.ini  to record these for every type of NIC of igb/ixgbe/i40e,
It seems very reasonable, but will DPDK community will agree to such a big change for this a specific feature?
 Maybe your suggestion of "in doc/guide/prog_guide/rte_flow.rst,  add  a short summary for each of them and a link to the
 relevant PMD documentation in nics/$PMD.rst ".
and also record to doc\guides\nics\ixgbe.rst will be the only feasible scheme?
Although it  will be too much to store.

Wenzhuo and Adrien, If none of you has no objection to this, I will implement as Adrien's first suggestion.

Thank you.
> 
> > > > -----Original Message-----
> > > > From: TETSURO NAKAMURA [mailto:nakamura.tetsuro@lab.ntt.co.jp]
> > > > Sent: Wednesday, August 2, 2017 12:22 PM
> > > > To: Zhao1, Wei <wei.zhao1@intel.com>
> > > > 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
> > > >
> > > > Wei Zhao - san
> > > > (Cc'ing Wenzhuo - san)
> > > >
> > > > According to the e-mail thread [1] in April, you have a document
> > > > about command format when creating flows on ixgbe NIC.
> > > >
> > > > I would appreciate your uploading that document to community or
> > > > could you just share it with me via an e-mail ??
> > > >
> > > > [1] http://dpdk.org/ml/archives/users/2017-April/001786.html
> > > >
> > > > Thanks,
> > > >
> > > > Tetsuro
> > > >
> > > > # re-sending the e-mail because I failed to submit the e-mail to
> > > > users@dpdk.org.
> > > >
> > > > --
> > > > Tetsuro Nakamura <nakamura.tetsuro@lab.ntt.co.jp> NTT Network
> > > > Service Systems Laboratories
> > > > TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11,
> > > > Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan
> > > >
> >
> 
> --
> Adrien Mazarguil
> 6WIND

  reply	other threads:[~2017-08-07  8:33 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 [this message]
2017-08-08  8:57         ` Ferruh Yigit
2017-08-29  7:26           ` 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=A2573D2ACFCADC41BB3BE09C6DE313CA07C45503@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --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=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).