All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Mikael Pettersson <mikpelinux@gmail.com>,
	Finn Thain <fthain@telegraphics.com.au>,
	Michael Schmitz <schmitzmic@gmail.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs
Date: Tue, 31 May 2016 12:41:04 +0200	[thread overview]
Message-ID: <CAMuHMdWfs9jEnR=g=pACg31cbnab2sxRXtjN5nc4TFj-=umtqA@mail.gmail.com> (raw)
In-Reply-To: <2782d89d-8baa-c4b1-b1cc-4a48008ef1fa@physik.fu-berlin.de>

Hi Adrian,

On Tue, May 31, 2016 at 12:39 PM, John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> 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@linux-m68k.org

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

  reply	other threads:[~2016-05-31 10:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 11:38 [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs Mikael Pettersson
2014-06-06 11:43 ` Geert Uytterhoeven
2014-06-06 13:11   ` Mikael Pettersson
2014-06-07 13:22     ` Mikael Pettersson
2014-06-11  8:20       ` Mikael Pettersson
2014-06-11  8:45 ` Andreas Schwab
2014-07-01 11:43   ` Mikael Pettersson
2015-03-31  1:16     ` Michael Schmitz
2015-03-31 13:19       ` Mikael Pettersson
2015-04-01  3:08         ` Michael Schmitz
2015-04-01  4:45           ` Finn Thain
2015-04-01  5:21             ` Michael Schmitz
2015-04-06 21:25             ` Michael Schmitz
2015-04-07  0:06               ` Finn Thain
2015-04-07  5:38                 ` Michael Schmitz
2016-02-21 17:06         ` Mikael Pettersson
2016-02-21 19:31           ` Michael Schmitz
2016-02-22 10:01           ` Geert Uytterhoeven
2016-03-06  7:21             ` Mikael Pettersson
2016-03-06  8:54               ` Geert Uytterhoeven
2016-03-06  9:20                 ` Mikael Pettersson
2016-04-13 18:57                   ` Mikael Pettersson
2016-05-31  4:52           ` Finn Thain
2016-05-31 10:06             ` Mikael Pettersson
2016-05-31 10:21               ` Geert Uytterhoeven
2016-05-31 10:39                 ` John Paul Adrian Glaubitz
2016-05-31 10:41                   ` Geert Uytterhoeven [this message]
2016-06-01  6:36                 ` Mikael Pettersson
2015-04-01 16:11       ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMuHMdWfs9jEnR=g=pACg31cbnab2sxRXtjN5nc4TFj-=umtqA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=fthain@telegraphics.com.au \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.org \
    --cc=mikpelinux@gmail.com \
    --cc=schmitzmic@gmail.com \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.