All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] mem: get memzone from any CPU socket when hugepages are disabled
Date: Fri, 26 Jul 2013 17:09:48 +0200	[thread overview]
Message-ID: <201307261709.48387.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <51F28E32.9060505-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>

26/07/2013 16:56, Damien Millescamps :
> On 07/26/2013 04:35 PM, Adrien Mazarguil wrote:
> > When huge pages are disabled, memory is allocated for a single, undefined
> > CPU socket using malloc(), causing rte_memzone_reserve_aligned() to fail
> > most of the time.
> > 
> > This patch causes that memory to use SOCKET_ID_ANY instead of 0, and
> > allow it to be used in place of any socket ID specified by user.
> > 
> > Signed-off-by: Adrien Mazarguil <adrien.mazarguil-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
> > ---
> > 
> >  lib/librte_eal/common/eal_common_memzone.c | 1 +
> >  lib/librte_eal/linuxapp/eal/eal_memory.c   | 2 +-
> >  2 files changed, 2 insertions(+), 1 deletion(-)
> 
> ack

applied

-- 
Thomas

      parent reply	other threads:[~2013-07-26 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 14:35 [PATCH] mem: get memzone from any CPU socket when hugepages are disabled Adrien Mazarguil
     [not found] ` <1374849329-21532-1-git-send-email-adrien.mazarguil-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 14:56   ` Damien Millescamps
     [not found]     ` <51F28E32.9060505-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 15:09       ` 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=201307261709.48387.thomas.monjalon@6wind.com \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.