From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>, Jim Murphy <jmurphy@arista.com>
Cc: "Ming Zhao(赵明)" <mzhao@luminatewireless.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
dev@dpdk.org
Subject: Re: [RFC 0/4] Use Google Test as DPDK unit test framework
Date: Fri, 05 Aug 2016 09:42:27 +0200 [thread overview]
Message-ID: <1568995.VcFoQ8Pk7z@xps13> (raw)
In-Reply-To: <CAE52828-EE15-41B3-BCE0-55A1274F2322@intel.com>
2016-08-04 19:55, Wiles, Keith:
>
> > On Aug 4, 2016, at 2:47 PM, Jim Murphy <jmurphy@arista.com> wrote:
> >
> > Hi,
> >
> > We are looking at using our existing test environment for our DPDK
> > applications that will run on our build servers. Hughpages therefore is an
> > issue. What is involved in running DPDK without huge pages?
>
> Command line option —no-huge should work. Note two dashs in front.
Most of drivers still require hugepages.
A big rework would be needed to make them work without hugepages.
next prev parent reply other threads:[~2016-08-05 7:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 20:37 [RFC 0/4] Use Google Test as DPDK unit test framework Declan Doherty
2016-08-02 20:37 ` [RFC 1/4] mk: Add support for C++ compilation Declan Doherty
2016-08-02 20:37 ` [RFC 2/4] examples: add c++ example application Declan Doherty
2016-08-02 20:37 ` [RFC 3/4] eal: add command line option to log output to stdout Declan Doherty
2016-08-03 11:25 ` Neil Horman
2016-08-02 20:37 ` [RFC 4/4] app/test-gtest: example google test application Declan Doherty
2016-08-02 21:52 ` [RFC 0/4] Use Google Test as DPDK unit test framework Thomas Monjalon
2016-08-03 9:16 ` Remy Horton
2016-08-03 9:57 ` Doherty, Declan
2016-08-03 12:51 ` Neil Horman
2016-08-03 20:46 ` Ming Zhao(赵明)
2016-08-04 19:47 ` Jim Murphy
2016-08-04 19:55 ` Wiles, Keith
2016-08-05 7:42 ` Thomas Monjalon [this message]
2016-08-05 7:41 ` Yerden Zhumabekov
2016-08-05 9:11 ` Remy Horton
2016-08-05 12:59 ` Neil Horman
2016-08-05 14:54 ` Remy Horton
2016-08-03 11:31 ` Neil Horman
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=1568995.VcFoQ8Pk7z@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jmurphy@arista.com \
--cc=keith.wiles@intel.com \
--cc=mzhao@luminatewireless.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.