DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH RFC] eal: change default per socket memory allocation
Date: Tue, 6 May 2014 15:56:39 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697592AC7BB@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <3138330.LfuR0euKkp@xps13>

Hi Thomas,

> Having --socket-mem option to explicitly configure NUMA is OK.
> Having -m option for simple configuration is OK.

Exactly. No explicit requirements - use -m option. Explicit socket requirements - use --socket-mem option.

> So I don't understand why we shouldn't do this enhancement. I don't know if
> "overcomplication" is a good argument.

I don't see any reasons *for* this change. IMO this patch tries to fix a problem that doesn't exist (or, rather, a problem that is already solved with --socket-mem switch). I'm open to persuasion on that one of course, but so far I don't see any compelling reason to change -m switch to be more like --socket-mem switch when we already have the --socket-mem switch for cases when the user cares about where the memory comes from.

Best regards,
Anatoly Burakov
DPDK SW Engineer


 

  reply	other threads:[~2014-05-06 15:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 14:15 David Marchand
2014-05-01 16:06 ` Burakov, Anatoly
2014-05-02  8:54   ` Burakov, Anatoly
2014-05-02  9:05     ` Venkatesan, Venky
2014-05-05  9:26       ` David Marchand
2014-05-06 10:05         ` Burakov, Anatoly
2014-05-06 15:18           ` Thomas Monjalon
2014-05-06 15:56             ` Burakov, Anatoly [this message]
2014-05-07 14:56         ` Venkatesan, Venky

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=C6ECDF3AB251BE4894318F4E45123697592AC7BB@IRSMSX101.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).