DPDK patches and discussions
 help / color / mirror / Atom feed
From: Panu Matilainen <pmatilai@redhat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] Provide reasonable default to -n
Date: Thu, 15 Oct 2015 14:49:03 +0300	[thread overview]
Message-ID: <cover.1444909165.git.pmatilai@redhat.com> (raw)
In-Reply-To: <d209690bda34d966299f000d63c0451b969262b0.1444818124.git.pmatilai@redhat.com>

The number of memory channels is a truly obscure thing as a mandatory
command line argument when its really just an optimization.
Provide a reasonable default in mempool as suggested by Bruce Richardson
and make the -n argument optional in EAL to make DPDK that little bit
easier to use for a first-timer.

Panu Matilainen (2):
  mempool: use a better default for number of memory channels
  eal: make the -n argument optional

 lib/librte_eal/common/eal_common_options.c | 8 +-------
 lib/librte_mempool/rte_mempool.c           | 2 +-
 2 files changed, 2 insertions(+), 8 deletions(-)

-- 
2.4.3

  parent reply	other threads:[~2015-10-15 11:49 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 ` Panu Matilainen [this message]
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
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=cover.1444909165.git.pmatilai@redhat.com \
    --to=pmatilai@redhat.com \
    --cc=dev@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).