[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <94cf610f-440d-a35d-9dc0-7c4941f03386@arm.com>
Date: Fri, 23 Aug 2019 08:30:54 +0000
From: James Clark <James.Clark@....com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
CC: "peterz@...radead.org" <peterz@...radead.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"alexander.shishkin@...ux.intel.com"
<alexander.shishkin@...ux.intel.com>,
"jolsa@...hat.com" <jolsa@...hat.com>,
"namhyung@...nel.org" <namhyung@...nel.org>,
"alexey.budankov@...ux.intel.com" <alexey.budankov@...ux.intel.com>,
"linux-perf-users@...r.kernel.org" <linux-perf-users@...r.kernel.org>,
nd <nd@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jeremy Linton <Jeremy.Linton@....com>
Subject: Re: [PATCH] Fixes hang in zstd compression test by changing the
source of random data.
Sorry about that, I will look into it.
Thanks
James
On 22/08/2019 22:24, Arnaldo Carvalho de Melo wrote:
> Em Thu, Aug 22, 2019 at 06:24:07PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Thu, Aug 22, 2019 at 01:55:15PM +0000, James Clark escreveu:
>>> Running 'perf test' with zstd compression linked will hang at the test
>>> 'Zstd perf.data compression/decompression' because /dev/random blocks
>>> reads until there is enough entropy. This means that the test will
>>> appear to never complete unless the mouse is continually moved while
>>> running it.
>>
>> message came mangled, had to do it by hand and then hook up your header
>> so as to get the correct date, attribution, etc, please check
>> Documentation/process/email-clients.rst,
>
> Having said that, thanks, applied.
>
> - Arnaldo
>
Powered by blists - more mailing lists