From: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dts] [PATCH V2 0/2] [next]dts/pktgen: TREX core mask configuration
Date: Tue, 6 Aug 2019 06:13:14 +0000 [thread overview]
Message-ID: <9DEEADBC57E43F4DA73B571777FECECA41D770B0@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1565071409-215899-1-git-send-email-yufengx.mo@intel.com>
Acked-by: Zhaoyan Chen <zhaoyan.chen@intel.com>
Regards,
Zhaoyan Chen
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yufengmx
> Sent: Tuesday, August 6, 2019 2:03 PM
> To: dts@dpdk.org
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V2 0/2] [next]dts/pktgen: TREX core mask configuration
>
> convert core mask setting to list format.
>
>
> v2:
> - Follow Chen, Zhaoyan review
> - *. remove synchronized option for future
> - *. add CORE_MASK_PIN option value
>
> yufengmx (2):
> [next]conf/pktgen: update option description
> [next]framework/pktgen_trex: convert core mask setting to list format
>
> conf/pktgen.cfg | 11 +++++++++--
> framework/pktgen_trex.py | 26 +++++++++++++++++++++-----
> 2 files changed, 30 insertions(+), 7 deletions(-)
>
> --
> 1.9.3
next prev parent reply other threads:[~2019-08-06 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 6:03 yufengmx
2019-08-06 6:03 ` [dts] [PATCH V2 1/2] [next]conf/pktgen: update option description yufengmx
2019-08-06 6:13 ` Chen, Zhaoyan
2019-08-06 6:03 ` [dts] [PATCH V2 2/2] [next]framework/pktgen_trex: convert core mask setting to yufengmx
2019-08-06 6:13 ` Chen, Zhaoyan
2019-08-06 6:13 ` Chen, Zhaoyan [this message]
2019-08-07 1:44 ` [dts] [PATCH V2 0/2] [next]dts/pktgen: TREX core mask configuration Tu, Lijuan
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=9DEEADBC57E43F4DA73B571777FECECA41D770B0@SHSMSX104.ccr.corp.intel.com \
--to=zhaoyan.chen@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@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).