patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: dev <dev@dpdk.org>, David Wilder <dwilder@us.ibm.com>,
	Luca Boccassi <bluca@debian.org>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] build: reduce max_lcores for ppc
Date: Tue, 04 May 2021 15:16:36 +0200	[thread overview]
Message-ID: <2433893.oCF5k2Ffog@thomas> (raw)
In-Reply-To: <CAMw=ZnT4=7TCzZgaFRjaVuBhzTR7e_AYXeJUjESxrxOEoeW98A@mail.gmail.com>

29/04/2021 13:28, Luca Boccassi:
> On Wed, 28 Apr 2021 at 21:10, David Christensen <drc@linux.vnet.ibm.com>
> wrote:
> >
> > When setting RTE_MAX_LCORES to the maximum value supported by ppc
> > hardware (1536), the lcores_autotest may timeout after 30 seconds
> > because the test takes nearly 60 seconds to complete. Set max_lcores to
> > a lower value because the maximum value is unlikely to be seen in any
> > production systems and to eliminate the quick test timeout error.

The compromise is documented, so the config exception is acceptable.

> > Bugzilla ID: 684
> > Fixes: db1f2f8a9fe5 ("config: increase maximum lcores for ppc")
> > Cc: dwilder@us.ibm.com

Cc: stable@dpdk.org

> >
> > Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
> > ---
> >  config/ppc/meson.build | 17 ++++++++++++++---
> >  1 file changed, 14 insertions(+), 3 deletions(-)
> 
> Acked-by: Luca Boccassi <bluca@debian.org>

Applied, thanks






           reply	other threads:[~2021-05-04 13:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAMw=ZnT4=7TCzZgaFRjaVuBhzTR7e_AYXeJUjESxrxOEoeW98A@mail.gmail.com>]

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=2433893.oCF5k2Ffog@thomas \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=dwilder@us.ibm.com \
    --cc=stable@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).