From: Matthew Hall <mhall@mhcomputing.net>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PKTGEN] [PATCH 1/2] usage_pktgen.rst: multiple instances: clean up section intro
Date: Fri, 22 Jan 2016 21:46:31 -0500 [thread overview]
Message-ID: <20160123024631.GA25867@mhcomputing.net> (raw)
In-Reply-To: <8A27B71D-329B-4AF5-85BD-81B4904E142D@intel.com>
On Thu, Jan 21, 2016 at 03:46:21PM +0000, Wiles, Keith wrote:
> It appears (if I compared the text correctly) the above only move a few
> trailing words to the next line, why?
I believe in trying to leave code / docs cleaner than I found them.
Most Markdown / ReStructured Text has a tradition of 78-character wide line
length limits.
So just trying to make the world a better place. That's it.
> Maybe this is clearer.
>
> If you are running pktgen and your application together, you have to start up
> each one a bit differently to make sure they share the resources like memory,
> huge page files and ports. I will use two Pktgens running on the same machine,
> which just means you have imagine your application as one of the Pktgen instances.
I'll make some adjustments when I get more time and try again.
In general I think it would be good if we had a bit more of a forest view of
trying to make docs for all of the things pktgen docs are missing and not get
too hung up on one tree or another.
I don't necessarily have a ton of time for editing these to the Nth degree,
but I do want to make life better for the next confused people to avoid a
storm of duplicate comments and issues.
Matthew.
prev parent reply other threads:[~2016-01-23 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:50 Matthew Hall
2016-01-21 5:50 ` [dpdk-dev] [PKTGEN] [PATCH 2/2] usage_pktgen.rst: multiple instances: clarify EAL options needed Matthew Hall
2016-01-21 15:40 ` Wiles, Keith
2016-01-21 15:46 ` [dpdk-dev] [PKTGEN] [PATCH 1/2] usage_pktgen.rst: multiple instances: clean up section intro Wiles, Keith
2016-01-23 2:46 ` Matthew Hall [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=20160123024631.GA25867@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=keith.wiles@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).