From: TETSURO NAKAMURA <nakamura.tetsuro@lab.ntt.co.jp>
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" <dev@dpdk.org>
Subject: Re: [dpdk-dev] using rte_flow via tespmd with Intel X552
Date: Wed, 2 Aug 2017 18:02:11 +0900 [thread overview]
Message-ID: <5a75cfb3-6956-0dc7-2d83-8c7d957b16be@lab.ntt.co.jp> (raw)
In-Reply-To: <A2573D2ACFCADC41BB3BE09C6DE313CA07C333AA@PGSMSX103.gar.corp.intel.com>
Hi Zhao1, Wei - san,
I really appreciate your help !
I have no idea where to upload this,
but I'm sure it should be uploaded to somewhere public.
On 2017/08/02 16:28, Zhao1, Wei wrote:
> 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?
>
>
>
>> -----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
>>
>
--
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
next prev parent reply other threads:[~2017-08-02 9:02 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 [this message]
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
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=5a75cfb3-6956-0dc7-2d83-8c7d957b16be@lab.ntt.co.jp \
--to=nakamura.tetsuro@lab.ntt.co.jp \
--cc=dev@dpdk.org \
--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).