From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>,
Vamsi Attunuru <vattunuru@marvell.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] test: fix --socket-mem option in eal flag autotest
Date: Tue, 30 Jul 2019 11:24:34 +0200 [thread overview]
Message-ID: <2470917.OEGRKAZCeL@xps> (raw)
In-Reply-To: <1564387730-2164-1-git-send-email-david.marchand@redhat.com>
29/07/2019 10:08, David Marchand:
> From: Vamsi Attunuru <vattunuru@marvell.com>
>
> eal flag autotest fails when multiple mem size flags are passed to
> --socket-mem option irrespective of RTE_MAX_NUMA_NODES and the number of
> available sockets on the test system.
>
> Fixes: 45f1b6e8680a ("app: add new tests on eal flags")
> Cc: stable@dpdk.org
>
> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Reviewed-by: Vamsi Attunuru <vattunuru@marvell.com>
> Tested-by: Vamsi Attunuru <vattunuru@marvell.com>
Applied, thanks
prev parent reply other threads:[~2019-07-30 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 7:25 [dpdk-dev] [PATCH v1 1/1] app/test: fix --socket-mem option in eal flag autotest Vamsi Attunuru
2019-04-10 8:26 ` David Marchand
2019-04-10 11:43 ` [dpdk-dev] [EXT] " Vamsi Krishna Attunuru
2019-07-11 5:15 ` [dpdk-dev] [PATCH v2 " vattunuru
2019-07-11 13:56 ` Aaron Conole
2019-07-12 6:43 ` [dpdk-dev] [PATCH v3 " vattunuru
2019-07-23 6:13 ` Vamsi Krishna Attunuru
2019-07-26 13:39 ` David Marchand
2019-07-28 4:19 ` [dpdk-dev] [EXT] " Vamsi Krishna Attunuru
2019-07-29 8:08 ` [dpdk-dev] [PATCH v4] test: " David Marchand
2019-07-30 9:24 ` Thomas Monjalon [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=2470917.OEGRKAZCeL@xps \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=vattunuru@marvell.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.