DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@6wind.com>
To: Chao Zhu <chaozhu@linux.vnet.ibm.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Fwd: [PATCH] PPC: Fix NUMA node numbering on IBM POWER8 LE machine
Date: Wed, 16 Sep 2015 10:09:16 +0200	[thread overview]
Message-ID: <CALwxeUvQBOt7FAMn49rE+FuDbitwFvy2kswDCjDUhZvs_se49g@mail.gmail.com> (raw)
In-Reply-To: <55F8CDC4.9040409@linux.vnet.ibm.com>

Hello Chao,

On Wed, Sep 16, 2015 at 4:02 AM, Chao Zhu <chaozhu@linux.vnet.ibm.com>
wrote:

> Actually, without this change, DPDK can't work properly on PPC64 little
> endian platform. It'll report "EAL: Not enough memory available! Requested:
> xxxMB, available: xxxMB" such kind of error. But for users, they don't know
> that changing the value of CONFIG_RTE_MAX_NUMA_NODES can fix this.  That
> why I invoke this patch.


Sorry, I forgot to reply in this thread.

Well, to me, this is a workaround.
Yes it will work, but what happens if tomorrow we have some hardware that
tells us that it has some numa node which 60000 index ?

I think we need a rework in eal to proerly handle this, like I said in this
mail :
http://dpdk.org/ml/archives/dev/2015-September/023630.html

Do you think you can look into this ?


Thanks.

-- 
David Marchand

  reply	other threads:[~2015-09-16  8:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 12:19 [dpdk-dev] " Chao Zhu
2015-09-15  7:46 ` [dpdk-dev] Fwd: " Chao Zhu
2015-09-15  9:01   ` Bruce Richardson
2015-09-16  2:02     ` Chao Zhu
2015-09-16  8:09       ` David Marchand [this message]
2015-09-17  8:56         ` Chao Zhu

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=CALwxeUvQBOt7FAMn49rE+FuDbitwFvy2kswDCjDUhZvs_se49g@mail.gmail.com \
    --to=david.marchand@6wind.com \
    --cc=chaozhu@linux.vnet.ibm.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).