From: David Marchand <david.marchand@6wind.com>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal_common_options: Allow combining -m and --no-huge
Date: Wed, 27 May 2015 09:43:09 +0200 [thread overview]
Message-ID: <CALwxeUtOW7o5PCpG0vXhp9JqOppw+71aEtnFXud2U1HaXnKKpQ@mail.gmail.com> (raw)
In-Reply-To: <20150520142427.4b977210@miho>
Hello Simon,
On Wed, May 20, 2015 at 2:24 PM, Simon Kagstrom <
simon.kagstrom@netinsight.net> wrote:
> Needed to run as non-root but with higher memory allocations.
>
> Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
> Signed-off-by: Johan Faltstrom <johan.faltstrom@netinsight.net>
> ---
> lib/librte_eal/common/eal_common_options.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/common/eal_common_options.c
> b/lib/librte_eal/common/eal_common_options.c
> index 8fcb1ab..89b867d 100644
> --- a/lib/librte_eal/common/eal_common_options.c
> +++ b/lib/librte_eal/common/eal_common_options.c
> @@ -851,8 +851,8 @@ eal_check_common_options(struct internal_config
> *internal_cfg)
> return -1;
> }
> if (internal_cfg->no_hugetlbfs &&
> - (mem_parsed || internal_cfg->force_sockets == 1)) {
> - RTE_LOG(ERR, EAL, "Options -m or --"OPT_SOCKET_MEM" cannot
> "
> + (internal_cfg->force_sockets == 1)) {
> + RTE_LOG(ERR, EAL, "Option --"OPT_SOCKET_MEM" cannot "
> "be specified together with --"OPT_NO_HUGE"\n");
> return -1;
> }
>
Hum, déjà vu.
Well, I asked some question last time :
http://dpdk.org/ml/archives/dev/2015-March/015867.html
This patch looks good but since I don't use this --no-huge that often, I
would like to know how you tested this.
And please, when resending a patch, it should be marked as vX.
--
David Marchand
next prev parent reply other threads:[~2015-05-27 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 12:24 Simon Kagstrom
2015-05-27 7:29 ` Mcnamara, John
2015-05-27 7:43 ` David Marchand [this message]
2015-05-27 8:09 ` Simon Kågström
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=CALwxeUtOW7o5PCpG0vXhp9JqOppw+71aEtnFXud2U1HaXnKKpQ@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=simon.kagstrom@netinsight.net \
/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).