From: "Liu, Yong" <yong.liu@intel.com>
To: "xu,huilong" <huilongx.xu@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH V2 1/2] add fdir test case in plan
Date: Wed, 08 Mar 2017 15:53:45 +0800 [thread overview]
Message-ID: <58BFB889.1020205@intel.com> (raw)
In-Reply-To: <1488334580-41742-1-git-send-email-huilongx.xu@intel.com>
Huilong,
Please try your best to keep each line in 79 characters. Another comment
is that, need indication about which kind of NICs support IPv4
tos/proto/ttl and ipv6 tc/nh/hop-limits.
Thanks,
Marvin
On 03/01/2017 10:16 AM, xu,huilong wrote:
> -connected to the traffic generator. If this is not the case, the following
> +connected to the traffic generator. All fdir cmdline please see doc onhttp://www.dpdk.org/doc/guides/testpmd_app_ug/testpmd_funcs.html#filter-functions. If this is not the case, the following
> ``testpmd`` commands must be changed, and also the ``--portmask`` parameter.
>
prev parent reply other threads:[~2017-03-08 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 2:16 xu,huilong
2017-03-01 2:16 ` [dts] [PATCH V2 2/2] add fdir test code for new case xu,huilong
2017-03-08 2:40 ` Xu, HuilongX
2017-03-08 7:54 ` Liu, Yong
2017-03-08 7:53 ` Liu, Yong [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=58BFB889.1020205@intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=huilongx.xu@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).