DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Babu Radhakrishnan,
	AgalyaX" <agalyax.babu.radhakrishnan@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/test: enhance meson test run for FreeBSD and Linux
Date: Fri, 26 Apr 2019 14:53:31 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A44B7F0@irsmsx110.ger.corp.intel.com> (raw)
Message-ID: <20190426145331.TtDJSxkJoQuZuBWNq3nwBle_GlAb_8wRspU9vH29rCw@z> (raw)
In-Reply-To: <1551863976-14093-1-git-send-email-agalyax.babu.radhakrishnan@intel.com>



> -----Original Message-----
> From: Babu Radhakrishnan, AgalyaX
> Sent: Wednesday, March 6, 2019 9:20 AM
> To: dev@dpdk.org
> Cc: Pattan, Reshma <reshma.pattan@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Babu Radhakrishnan, AgalyaX
> <agalyax.babu.radhakrishnan@intel.com>
> Subject: [PATCH] app/test: enhance meson test run for FreeBSD and Linux
> 
> From: Agalya Babu RadhaKrishnan <agalyax.babu.radhakrishnan@intel.com>
> 
> 1)For linux, running all tests on same cores can increase failure rate.
> So instead run each test case on separate lcore using -l EAL option.
> Lcore for each test case will be selected in the incremental order of 0,1,2 ... till it
> reaches the maximum available cores in the system which can be known from
> 'nproc' command.
> On the other hand, by default meson runs all tests in parallel in different threads
> which can be controlled by MESON_TESTTHREAD option.
> eg. MESON_TESTTHREAD=4 meson test --suite DPDK:fast-tests
> 
> 2)FreeBSD dont support file-prefix, so  changes are made to run the tests
> without 'file-prefix'option.
> eg. meson test --suite DPDK:fast-tests
> 
> Signed-off-by: Agalya Babu RadhaKrishnan
> <agalyax.babu.radhakrishnan@intel.com>

Nacking this patch , as the similar patch http://patches.dpdk.org/patch/52730/ has been accepted.
Nacked-by: Reshma Pattan <reshma.pattan@intel.com> 


  parent reply	other threads:[~2019-04-26 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  9:19 Agalya Babu RadhaKrishnan
2019-04-01 12:32 ` Pattan, Reshma
2019-04-01 12:32   ` Pattan, Reshma
2019-04-03 12:23 ` Pattan, Reshma
2019-04-03 12:23   ` Pattan, Reshma
2019-04-03 12:39 ` David Marchand
2019-04-03 12:39   ` David Marchand
2019-04-26 14:53 ` Pattan, Reshma [this message]
2019-04-26 14:53   ` Pattan, Reshma

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=3AEA2BF9852C6F48A459DA490692831F2A44B7F0@irsmsx110.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=agalyax.babu.radhakrishnan@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /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).