From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Paul Atkins <patkins@brocade.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mem: allow mem size to be specified when no hugetblfs
Date: Mon, 15 Jun 2015 15:54:45 +0200 [thread overview]
Message-ID: <4523834.AgJP7xiYyx@xps13> (raw)
In-Reply-To: <1432909438-21329-1-git-send-email-patkins@brocade.com>
2015-05-29 15:23, Paul Atkins:
> The config option to turn off huge table support does not work with
> the existing -m option to specify the amount of memory to use. Add
> a new option --no-huge-mem-size <mem in MB> that takes a paramater
> to use as the heap size instead of the value specified by
> MEMSIZE_IF_NO_HUGE_PAGE.
>
> Signed-off-by: Paul Atkins <patkins@brocade.com>
Instead of adding a new option, the constraint is removed by this patch:
http://dpdk.org/dev/patchwork/patch/4915/
That's why this patch is rejected.
Hope the above patch match your needs.
prev parent reply other threads:[~2015-06-15 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 14:23 Paul Atkins
2015-06-15 13:54 ` 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=4523834.AgJP7xiYyx@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=patkins@brocade.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).