From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas F Herbert <therbert@redhat.com>,
Simon Kagstrom <simon.kagstrom@netinsight.net>,
"dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@6wind.com" <david.marchand@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2] eal: Allow combining -m and --no-huge
Date: Wed, 27 May 2015 13:27:24 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2F2CDF8@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <5565C166.4090505@redhat.com>
> -----Original Message-----
> From: Thomas F Herbert [mailto:therbert@redhat.com]
> Sent: Wednesday, May 27, 2015 2:07 PM
> To: Simon Kagstrom; dev@dpdk.org; david.marchand@6wind.com; Mcnamara, John
> Subject: Re: [dpdk-dev] [PATCH v2] eal: Allow combining -m and --no-huge
>
>
>
> On 5/27/15 5:30 AM, Simon Kagstrom wrote:
> > Needed to run as non-root but with higher memory allocations, and
> > removes a constraint on no-huge mode being limited to 64M. A usage
> > example is if running with file input with the pcap PMD, which can be
> > done as non-root after this patch via e.g.,
> Simon,
>
> I just tried applying v2 of the patch to master:
> git apply ../patches/eal_common_options.patch
> error: patch failed: lib/librte_eal/common/eal_common_options.c:850
> error: lib/librte_eal/common/eal_common_options.c: patch does not apply
Hi Thomas,
I just tried it with the HEAD via pwclient and it applies cleanly:
$ git pull origin
Already up-to-date.
$ pwclient git-am 4915
Applying patch #4915 using 'git am'
Description: [dpdk-dev,v2] eal: Allow combining -m and --no-huge
Applying: eal: Allow combining -m and --no-huge
John.
--
next prev parent reply other threads:[~2015-05-27 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 9:30 Simon Kagstrom
2015-05-27 13:06 ` Thomas F Herbert
2015-05-27 13:27 ` Mcnamara, John [this message]
2015-05-27 13:29 ` Simon Kagstrom
2015-05-27 14:17 ` Thomas F Herbert
2015-06-15 14:04 ` David Marchand
2015-06-15 14:08 ` Thomas Monjalon
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=B27915DBBA3421428155699D51E4CFE2F2CDF8@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=simon.kagstrom@netinsight.net \
--cc=therbert@redhat.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).