From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Panu Matilainen <pmatilai@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] Provide reasonable default to -n
Date: Thu, 15 Oct 2015 13:12:20 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023833CF@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <561F9DD4.3070906@redhat.com>
> -----Original Message-----
> From: Panu Matilainen [mailto:pmatilai@redhat.com]
> Sent: Thursday, October 15, 2015 1:37 PM
> To: Mcnamara, John; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/2] Provide reasonable default to -n
>
> Sure. I was planning on going through the docs and updating them
> (separately) if the change is otherwise accepted, I suspect there are more
> than those two places needing changes.
Hi,
Good stuff.
I counted ~ 100 places in the docs where -n is used. I don't know if they all
have to be removed. The 2 examples I gave were the only ones that I found,
in a quick scan, that explicitly say -n is required. The rest are in the
"mostly harmless" category but if you wanted to remove the majority of the
references then that is probably okay.
John.
--
next prev parent reply other threads:[~2015-10-15 13:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 10:22 [dpdk-dev] [PATCH] eal: default to one memory channel if not specified Panu Matilainen
2015-10-14 11:45 ` David Marchand
2015-10-14 12:04 ` Panu Matilainen
2015-10-14 13:05 ` Bruce Richardson
2015-10-15 11:49 ` [dpdk-dev] [PATCH 0/2] Provide reasonable default to -n Panu Matilainen
2015-10-15 11:49 ` [dpdk-dev] [PATCH 1/2] mempool: use a better default for number of memory channels Panu Matilainen
2015-10-15 11:49 ` [dpdk-dev] [PATCH 2/2] eal: make the -n argument optional Panu Matilainen
2015-10-15 12:03 ` [dpdk-dev] [PATCH 0/2] Provide reasonable default to -n David Marchand
2015-10-26 16:51 ` Thomas Monjalon
2015-10-15 12:10 ` Mcnamara, John
2015-10-15 12:36 ` Panu Matilainen
2015-10-15 13:12 ` Mcnamara, John [this message]
2015-10-26 16:50 ` Thomas Monjalon
2015-10-26 16:56 ` Thomas Monjalon
2015-10-27 7:19 ` Panu Matilainen
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=B27915DBBA3421428155699D51E4CFE2023833CF@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=pmatilai@redhat.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).