From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2]doc:Add performance test guide about how to get DPDK high perf on Intel platform
Date: Thu, 17 Sep 2015 01:16:27 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E01DDD853@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <2130384.etnPeQ8t8i@xps13>
Thomas/John
Thanks a lot for your comments, and I will update the patch soon.
Thanks
Qian
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Wednesday, September 16, 2015 9:01 PM
To: Mcnamara, John
Cc: Xu, Qian Q; dev@dpdk.org; Jayakumar, Muthurajan
Subject: Re: [dpdk-dev][PATCH v2]doc:Add performance test guide about how to get DPDK high perf on Intel platform
2015-09-16 10:43, Mcnamara, John:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > --- /dev/null
> > > +++ b/doc/guides/perf_test_guide/index.rst
> >
> > Why creating a new guide?
> > Can it be included as a chapter of the Linux user guide?
>
> I think the subject is probably distinct enough to merit its own guide
> and it is more of an advanced topic than a getting started topic.
I think we should avoid creating too many guides.
This chapter is about using DPDK in Linux. Yes it is a bit more advanced than the Linux QSG. So why not creating an advanced section?
prev parent reply other threads:[~2015-09-17 1:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 3:19 Qian Xu
2015-08-18 1:16 ` Xu, Qian Q
2015-09-16 2:45 ` Xu, Qian Q
2015-09-16 8:21 ` Thomas Monjalon
2015-09-16 10:43 ` Mcnamara, John
2015-09-16 13:01 ` Thomas Monjalon
2015-09-17 1:16 ` Xu, Qian Q [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=82F45D86ADE5454A95A89742C8D1410E01DDD853@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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).