From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Xu, Qian Q" <qian.q.xu@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: Wed, 16 Sep 2015 10:43:48 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20233D3FA@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <2724688.VL6zfsszk2@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, September 16, 2015 9:22 AM
> To: Xu, Qian Q
> Cc: dev@dpdk.org; Jayakumar, Muthurajan; Mcnamara, John
> Subject: Re: [dpdk-dev][PATCH v2]doc:Add performance test guide about how
> to get DPDK high perf on Intel platform
>
> Hi,
>
> 2015-09-16 02:45, Xu, Qian Q:
> > Thomas
> > Could you help check my doc patch, and let me know anything needed for
> > the merge? I think it would be very helpful for the users to get high
> > performance with step-by-step guide. Thx.
>
> Yes it is useful.
> John and Siobhan are the maintainers for the doc.
Hi Qian,
The idea is good and a performance tuning guide would be very useful. I think that it could be structured a little differently to keep the Intel/non-Intel information separate and allow other maintainers to contribute sections.
> > --- /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.
+1 on the other comments.
John.
--
next prev parent reply other threads:[~2015-09-16 10:43 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 [this message]
2015-09-16 13:01 ` Thomas Monjalon
2015-09-17 1:16 ` Xu, Qian Q
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=B27915DBBA3421428155699D51E4CFE20233D3FA@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=qian.q.xu@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).