All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Nissim Nisimov <nissimn@radware.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: max MEMZONEs allowed
Date: Tue, 24 Nov 2015 08:44:07 +0000	[thread overview]
Message-ID: <56542357.4090901@intel.com> (raw)
In-Reply-To: <94AA676E9B9A384A844E7692F3CAD906C5548CD7@ILMB1.corp.radware.com>

On 23/11/2015 15:33, Nissim Nisimov wrote:
> Hi all,
>
> We are working on a system which requires allocating a big number of mem zones.
>
> We are now reaching the max limit of MEMZONEs allowed (RTE_MAX_MEMZONE).
>
> I see today dpdk limit the above number to 2560.
> Is there any specific reason for that? can I increase it in case needed. What may be the side effects of such changes?
>
You can increase the number of memsegs, 256 is just a default value.
The only side-effect I can think of, on systems that use more than the 
default number of memsegs, is slower EAL initialization and increased 
memseg lookup time.

Sergio
> Thx
> Nissim

      reply	other threads:[~2015-11-24  8:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 15:33 max MEMZONEs allowed Nissim Nisimov
2015-11-24  8:44 ` Sergio Gonzalez Monroy [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=56542357.4090901@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=nissimn@radware.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 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.