On 7/18/19 10:57 AM, Mel Gorman wrote:
> "howaboutsynergy" reported via kernel buzilla number 204165 that
> compact_zone_order was consuming 100% CPU during a stress test for
> prolonged periods of time. Specifically the following command, which
> should exit in 10 seconds, was taking an excessive
On Thu, 18 Jul 2019 11:48:10 + howaboutsyne...@protonmail.com wrote:
> > "howaboutsynergy" reported via kernel buzilla number 204165 that
>
>
> > I haven't included a Reported-and-tested-by as the reporters real name
> > is unknown but this was caught and repaired due to their testing and
>
‐‐‐ Original Message ‐‐‐
On Thursday, July 18, 2019 10:57 AM, Mel Gorman
wrote:
> "howaboutsynergy" reported via kernel buzilla number 204165 that
> I haven't included a Reported-and-tested-by as the reporters real name
> is unknown but this was caught and repaired due to their
"howaboutsynergy" reported via kernel buzilla number 204165 that
compact_zone_order was consuming 100% CPU during a stress test for
prolonged periods of time. Specifically the following command, which
should exit in 10 seconds, was taking an excessive time to finish while
the CPU was pegged at
4 matches
Mail list logo