; 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
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 remained after memzone autotest.
What if some existed initial memzone released during the test and some dirty
memzone remained. The counter cannot illustrate
Hi Anatoly,
I think your fix is elegant, however you can't grantee it doesn't have dirty
memzone remained after memzone autotest.
What if some existed initial memzone released during the test and some dirty
memzone remained. The counter cannot illustrate this state.
My fix just care about the m
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
4 matches
Mail list logo
