; nd
> Subject: Re: [dpdk-dev] [PATCH 2/2] test/memzone: handle previously allocated
> memzones
>
> On 31-Jan-18 7:51 AM, Phil Yang wrote:
> > Hi Anatoly,
> >
> > I think your fix is elegant, however you can't grantee it doesn't have dirty
> memzone remaine
combining both approaches. Is that OK with you?
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Anatoly Burakov
Sent: Saturday, January 27, 2018 1:41 AM
To: dev@dpdk.org
Cc: radoslaw.bierna...@linaro.org; sta...@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] test/memzon
bierna...@linaro.org; sta...@dpdk.org
> Subject: [dpdk-dev] [PATCH 2/2] test/memzone: handle previously allocated
> memzones
>
> Currently, memzone autotest expects there to be no memzones present by the
> time the test is run. Some hardware drivers will allocate memzones for
Thanks, looks OK for me.
Reviewed-by: Radoslaw Biernacki
adoslaw.bierna...@linaro.com>
On 26 January 2018 at 18:40, Anatoly Burakov
wrote:
> Currently, memzone autotest expects there to be no memzones
> present by the time the test is run. Some hardware drivers
> will allocate memzones for int
Currently, memzone autotest expects there to be no memzones
present by the time the test is run. Some hardware drivers
will allocate memzones for internal use during initialization,
resulting in tests failing due to unexpected memzones being
allocated before the test was run.
Fix this by making ca
5 matches
Mail list logo
