DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, laszlo.madarassy@ericsson.com, janos.kobor@ericsson.com
Subject: Re: [dpdk-dev] [PATCH] malloc: fix external heap allocation in no huge mode
Date: Fri, 26 Oct 2018 22:27:59 +0200	[thread overview]
Message-ID: <140058911.RUMSLY2u8S@xps> (raw)
In-Reply-To: <0a032f701099558dfbe4c9684df90874583a4544.1540465344.git.anatoly.burakov@intel.com>

25/10/2018 13:06, Anatoly Burakov:
> When no-huge mode is enabled, we always overwrite the socket ID to be
> SOCKET_ID_ANY in rte_malloc, because there is no NUMA awareness in no-huge
> mode. However, with external memory support, a socket ID may have other
> meaning, and we cannot overwrite the socket ID in those cases.
> 
> Fixes: 65ff37b105f7 ("malloc: add function to check if socket is external")
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied, thanks

      reply	other threads:[~2018-10-26 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 11:06 Anatoly Burakov
2018-10-26 20:27 ` Thomas Monjalon [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=140058911.RUMSLY2u8S@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=janos.kobor@ericsson.com \
    --cc=laszlo.madarassy@ericsson.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).