From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Michael Santana <msantana@redhat.com>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v1 1/1] app/test: fix --socket-mem option in eal flag autotest
Date: Wed, 10 Apr 2019 11:43:42 +0000 [thread overview]
Message-ID: <BYAPR18MB2631DD477D7B7424C6BA9E77A62E0@BYAPR18MB2631.namprd18.prod.outlook.com> (raw)
Message-ID: <20190410114342.HYrrS2UpS02tTnZuldbhj6Xra1YWeIQAchKK5PHoxU4@z> (raw)
In-Reply-To: <CAJFAV8zyhoCYh3cW0iFFGe1bRALJVYN+5JxtTY2cT_ChaWG9cg@mail.gmail.com>
________________________________
From: David Marchand <david.marchand@redhat.com>
Sent: Wednesday, April 10, 2019 1:56 PM
To: Vamsi Krishna Attunuru
Cc: dev; Michael Santana; Aaron Conole
Subject: [EXT] Re: [dpdk-dev] [PATCH v1 1/1] app/test: fix --socket-mem option in eal flag autotest
External Email
________________________________
On Wed, Apr 10, 2019 at 9:26 AM Vamsi Attunuru <vattunuru@marvell.com<mailto:vattunuru@marvell.com>> wrote:
"argv2[]" positive test case fails with RTE_MAX_NUMA_NODES=1 config
because of "--socket-mem=0,0,0,0" option, which passes memory sizes
for multiple sockets. This patch fixes the issue by passing memory
size for node 0 alone.
How about modifying the test so that it also validates the format is consistent with the RTE_MAX_NUMA_NODES value ?
Vamsi > Yes, started working on it, it should also fix other negative tests(false negative) beneath argv2[] test.
--
David Marchand
next prev parent reply other threads:[~2019-04-10 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 7:25 [dpdk-dev] " Vamsi Attunuru
2019-04-10 7:25 ` Vamsi Attunuru
2019-04-10 8:26 ` David Marchand
2019-04-10 8:26 ` David Marchand
2019-04-10 11:43 ` Vamsi Krishna Attunuru [this message]
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
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=BYAPR18MB2631DD477D7B7424C6BA9E77A62E0@BYAPR18MB2631.namprd18.prod.outlook.com \
--to=vattunuru@marvell.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=msantana@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).