From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] test/malloc: run realloc tests on external heap
Date: Fri, 17 Apr 2020 13:12:36 +0100 [thread overview]
Message-ID: <c8c5c441-302f-15be-19b0-4a4b274d383b@intel.com> (raw)
In-Reply-To: <CAJFAV8y8Libw7cJ6D4trDTyMeoyyLhYwkkeBqwNPvbsYnoC-zQ@mail.gmail.com>
On 10-Apr-20 12:19 PM, David Marchand wrote:
> Hello Anatoly,
>
> On Thu, Apr 2, 2020 at 11:07 AM Anatoly Burakov
> <anatoly.burakov@intel.com> wrote:
>>
>> Due to the fact that the rte_realloc() test depends on the layout of
>> underlying memory, it can sometimes fail due to fragmentation of the
>> memory. To address this, make it so that the realloc autotests are run
>> using a newly created external memory heap instead of main memory.
>>
>> Bugzilla ID: 424
>
> Is it worth backporting?
> Thanks.
>
>
I don't think so. It's a very low priority issue and not really a bug.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-04-17 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 13:11 [dpdk-dev] [PATCH " Anatoly Burakov
2020-04-01 13:11 ` [dpdk-dev] [PATCH 2/2] test/malloc: add bad parameter tests for realloc Anatoly Burakov
2020-04-02 2:43 ` David Christensen
2020-04-02 2:40 ` [dpdk-dev] [PATCH 1/2] test/malloc: run realloc tests on external heap David Christensen
2020-04-02 9:02 ` [dpdk-dev] [PATCH v2 " Anatoly Burakov
2020-04-02 19:54 ` David Christensen
2020-04-21 16:16 ` David Marchand
2020-04-10 11:19 ` David Marchand
2020-04-17 12:12 ` Burakov, Anatoly [this message]
2020-04-02 9:02 ` [dpdk-dev] [PATCH v2 2/2] test/malloc: add bad parameter tests for realloc Anatoly Burakov
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=c8c5c441-302f-15be-19b0-4a4b274d383b@intel.com \
--to=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.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).