Hi Adrian,
On Tue, May 31, 2016 at 12:39 PM, John Paul Adrian Glaubitz
<glaubitz@xxxxxxxxxxxxxxxxxxx> wrote:
On 05/31/2016 12:21 PM, Geert Uytterhoeven wrote:
That's upstream commit c33bd8354f3a3bb26a98d2b6bf600b7b35657328?
Well done! Looks indeed like a suspect for the behavior you're seeing.
I suppose you will follow up with the mm people?
Yay, great news. I'm currently building a native GHC package for Debian/m68k
on Aranym and [kswapd] is taking around half of the CPU load. The suggestion
with drop_caches doesn't help all the time, unfortunately, so I'm really
looking forward getting this fixed :).
I expect the bad commit can just be reverted, as the surrounding code hasn't
changed?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
