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

2014-05-06 10:05, Burakov, Anatoly:
> David Marchand:
> > Actually, if we don't care where memory is allocated, we can at least try
> > to have the more common setup work properly (i.e. spread memory
> > allocations based on used cores).
> > I can see no usual setup where you
> > want to use cores on a socket while having all memory on another socket
> > but still expect performance to be good. 
> > So here is another approach for Didier's patch.
> > We can try to spread memory on numa sockets, if this fails, then we
> > default to previous behavior but leave a trace with a warning log "Could
> > not spread memory on numa sockets".
> > What do you think about this ?
> 
> Sounds like an overcomplication to me. There could be cases where
> performance doesn't matter, for example the -m switch could be used to run
> various tests (unit tests, functional tests etc.). For anything
> performance-related, the recommended option is to use --socket-mem,
> especially if you have NICs on specific sockets. Presumably, when you're
> setting up a coremask, you already know which sockets your cores are on, so
> I don't see a problem with specifying which sockets you want memory from.

Having --socket-mem option to explicitly configure NUMA is OK.
Having -m option for simple configuration is OK.
Making -m option working for most use cases would be really nice.
So I don't understand why we shouldn't do this enhancement. I don't know if 
"overcomplication" is a good argument. Maybe we should wait the patch to 
discuss it.

-- 
Thomas

  reply	other threads:[~2014-05-06 15:18 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 [this message]
2014-05-06 15:56             ` Burakov, Anatoly
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=3138330.LfuR0euKkp@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=anatoly.burakov@intel.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).