From: David Marchand <david.marchand@redhat.com>
To: Pallantla Poornima <pallantlax.poornima@intel.com>
Cc: dev <dev@dpdk.org>, "Pattan, Reshma" <reshma.pattan@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/eal: add ut cases for in-memory and single-file-segment
Date: Wed, 26 Jun 2019 15:54:03 +0200 [thread overview]
Message-ID: <CAJFAV8x1DZ_qKBPSPZ4MZsO_KRxAweaFCQSck0bqFe1CgOtbiA@mail.gmail.com> (raw)
In-Reply-To: <1561556725-6671-1-git-send-email-pallantlax.poornima@intel.com>
On Wed, Jun 26, 2019 at 3:47 PM Pallantla Poornima <
pallantlax.poornima@intel.com> wrote:
> Added unit test case for eal command line 'in-memory' option
> which will cover below functions.
> get_seg_memfd()
> test_memfd_create()
> pagesz_flags()
>
> Added unit test case for eal command line 'single-file-segments' option
> which will cover resize_hugefile().
>
> Signed-off-by: Pallantla Poornima <pallantlax.poornima@intel.com>
> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
> v2: Removed snprintf as suggested
> ---
> app/test/test_eal_flags.c | 66 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 66 insertions(+)
>
> diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c
> index 9112c96d0..85f4fc64a 100644
> --- a/app/test/test_eal_flags.c
> +++ b/app/test/test_eal_flags.c
> @@ -1010,6 +1010,24 @@ test_file_prefix(void)
> const char *argv4[] = {prgname, "-c", "1", "-n", "2", "-m",
> DEFAULT_MEM_SIZE, "--file-prefix=" memtest2 };
>
> + /* primary process with inmemory mode */
> + const char * const argv5[] = {prgname, "-c", "1", "-n", "2", "-m",
> + DEFAULT_MEM_SIZE, "--in-memory" };
> +
> + /* primary process with memtest1 and inmemory mode */
> + const char * const argv6[] = {prgname, "-c", "1", "-n", "2", "-m",
> + DEFAULT_MEM_SIZE, "--in-memory",
> + "--file-prefix=" memtest1 };
> +
> + /* primary process with parent file-prefix and inmemory mode */
> + const char * const argv7[] = {prgname, "-c", "1", "-n", "2", "-m",
> + DEFAULT_MEM_SIZE, "--in-memory", "--file-prefix", prefix };
> +
> + /* primary process with memtest1 and single-file-segments mode */
> + const char * const argv8[] = {prgname, "-c", "1", "-n", "2", "-m",
> + DEFAULT_MEM_SIZE, "--single-file-segments",
> + "--file-prefix=" memtest1 };
> +
>
Same comment than http://patchwork.dpdk.org/patch/55169/
Please drop -n and -c options if there is no requirement for the tests to
run.
--
David Marchand
next prev parent reply other threads:[~2019-06-26 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:37 [dpdk-dev] [PATCH] test/eal: add ut cases for in-memory and single-file-segment Pallantla Poornima
2019-06-25 10:22 ` Burakov, Anatoly
2019-06-26 13:45 ` [dpdk-dev] [PATCH v2] " Pallantla Poornima
2019-06-26 13:54 ` David Marchand [this message]
2019-06-27 13:07 ` [dpdk-dev] [PATCH v3] " Pallantla Poornima
2019-07-02 7:48 ` David Marchand
2019-07-03 7:13 ` [dpdk-dev] [PATCH v4] " Pallantla Poornima
2019-07-04 21:35 ` 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=CAJFAV8x1DZ_qKBPSPZ4MZsO_KRxAweaFCQSck0bqFe1CgOtbiA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=pallantlax.poornima@intel.com \
--cc=reshma.pattan@intel.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).