From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: move testpmd guide with other tools
Date: Fri, 11 Nov 2016 00:02:13 +0100 [thread overview]
Message-ID: <2696537.77E6llNtKT@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20264D07D@IRSMSX103.ger.corp.intel.com>
2016-11-10 16:11, Mcnamara, John:
> I had a look at the html output before and after this patch and I don't quite agree with it. I see that you are trying to clean up and make the documentation more consistent but I don't know if this is the right way to do it.
>
> The problem is that TestPMD is a bit of an outlier. It isn't a sample application and it isn't really a test application despite the name (it is more of a tester application). Also I don't think that it is a tool/utility like the other apps in the target directory (if it is seen as a tool then it should be renamed to something like dpdk-tester for consistency). Testpmd also has quite a lot of documentation, more than any of our other apps or utilities, which again makes it an outlier.
Yes testpmd is not the same kind of tool as others. It helps for tests,
debugging and demos.
About the name, as it is packaged as part of the runtime, I think we should
find a better name. As you said it should start with "dpdk-" and it should
contain "net" as it does not test the crypto drivers.
Something like dpdk-testpmd-net.
> So my preference is to leave TestPMD in the high level index.
OK I understand your opinion.
> However, I do think the High level index should be cleaned up a bit and the items re-ordered into a more logical sequence. I'll submit a patch for that.
OK thanks
next prev parent reply other threads:[~2016-11-10 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 10:02 Thomas Monjalon
2016-11-10 16:11 ` Mcnamara, John
2016-11-10 23:02 ` Thomas Monjalon [this message]
2016-11-10 23:18 ` Wiles, Keith
2016-11-10 23:32 ` 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=2696537.77E6llNtKT@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).