From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] devtools: fix required memory for null test
Date: Fri, 22 Nov 2019 13:15:56 +0100 [thread overview]
Message-ID: <CAJFAV8xdG1S2-SOARZVfS2W7LMZfqC4RGZsJ0=Q8kfY49Xjo+A@mail.gmail.com> (raw)
In-Reply-To: <20191120092835.25325-1-thomas@monjalon.net>
On Wed, Nov 20, 2019 at 10:29 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> The testpmd fails in memory allocation since some ethdev structs
> have been extended.
> Increasing memory allocation from 150 to 300 MB makes it working again.
>
> Fixes: 436b3a6b6e62 ("ethdev: reserve space in main structs for extension")
Fixed with https://patchwork.dpdk.org/patch/63226/
Marking as rejected.
--
David Marchand
prev parent reply other threads:[~2019-11-22 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 9:28 Thomas Monjalon
2019-11-22 12:15 ` David Marchand [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='CAJFAV8xdG1S2-SOARZVfS2W7LMZfqC4RGZsJ0=Q8kfY49Xjo+A@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).