From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>, nd <nd@arm.com>
Subject: RE: meson test --test-args="--no-huge"
Date: Wed, 23 Feb 2022 18:48:25 +0000 [thread overview]
Message-ID: <DBAPR08MB5814CAB06EEA9A9AFE036720983C9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20220223180459.GA31155@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
> -----Original Message-----
> From: Tyler Retzlaff <roretzla@linux.microsoft.com>
> Sent: Wednesday, February 23, 2022 12:05 PM
> To: dev@dpdk.org
> Subject: meson test --test-args="--no-huge"
>
> noticing that meson test --test-args="--no-huge" has a pretty significant
> number of failures.
>
> given --no-huge isn't tested at all is there value in keeping no-huge support?
> or is this just unintentional since the --no-huge configuration isn't run in the CI
> pipelines?
>
> what's the promise from dpdk for --no-huge? deprecated? supported?
It needs to be supported. There have been cloud environments where huge page support was not available. We should add it to CI.
prev parent reply other threads:[~2022-02-23 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 18:04 Tyler Retzlaff
2022-02-23 18:48 ` Honnappa Nagarahalli [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=DBAPR08MB5814CAB06EEA9A9AFE036720983C9@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=roretzla@linux.microsoft.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).