From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Poole, James G" <james.g.poole@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>,
"Gilmore, Walter E" <walter.e.gilmore@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-web] [PATCH] add 16.11 performance report to documentation
Date: Thu, 15 Dec 2016 11:48:53 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202685D8D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <3571351.Ppr3Ib5sf1@xps13>
+ Qian, Tim
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, December 15, 2016 11:21 AM
> To: Poole, James G <james.g.poole@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Cc: web@dpdk.org; Gilmore, Walter E <walter.e.gilmore@intel.com>
> Subject: Re: [dpdk-web] [PATCH] add 16.11 performance report to
> documentation
>
> 2016-12-07 09:07, James Poole:
> >> + <h2>Performance Reports</h2>
> > + <ul>
> > + <li><a
> href="http://fast.dpdk.org/doc/perf/Intel_DPDK_R16_11_NIC_performance_report.pdf">DPDK 16.11 Performance Report</a>
> > + </ul>
>
> This first report is online at
> http://fast.dpdk.org/doc/perf/Intel_DPDK_R16_11_NIC_performance_report.pdf
>
> Before applying this web patch, I was thinking the title on the web page
> should better match the filename, i.e. adding "Intel" and "NIC" words.
> What do you think of "DPDK 16.11 Intel NIC Performance Report"?
Hi Thomas,
I think that name change would be okay.
John
next prev parent reply other threads:[~2016-12-15 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 9:07 James Poole
2016-12-07 16:08 ` Mcnamara, John
2016-12-15 11:20 ` Thomas Monjalon
2016-12-15 11:48 ` Mcnamara, John [this message]
2016-12-15 13:54 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE202685D8D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=james.g.poole@intel.com \
--cc=qian.q.xu@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=tim.odriscoll@intel.com \
--cc=walter.e.gilmore@intel.com \
--cc=web@dpdk.org \
/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).