From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: thousands of kworker processes with 4.7.x and 4.8-rc*
Date: Sun, 25 Sep 2016 20:22:29 +0200 [thread overview]
Message-ID: <1474827749.8570.12.camel@gmail.com> (raw)
In-Reply-To: <1474824072.3990.11.camel@gmail.com>
On Sun, 2016-09-25 at 19:21 +0200, Mike Galbraith wrote:
> On Sun, 2016-09-25 at 21:40 +0900, Tomasz Chmielewski wrote:
>
> > The problem is the allocator.
> >
> > -CONFIG_SLUB=y
> > +CONFIG_SLAB=y
> >
> >
> > With SLUB, I'm getting a handful of kworker processes, as expected.
> >
> > With SLAB, I'm getting thousands of kworker processes.
> >
> >
> > Not sure if that's expected behaviour or not.
>
> I seriously doubt 1500+ kworkers piling up is expected.
>
> 4.7.0-rc4 47
> 4.7.0-rc5 1592
>
> Presuming you didn't switch to SLAB and/or change userspace all around
> while testing, that would still indicate a kernel regression lurking
> between rc4 and rc5.
Nevermind, seems config change was how you met the thing.
FWIW, I turned on SLAB with a distro config here, and see no such
behavior. If I could reproduce, I'd take the busted config back to
older kernels.
-Mike
next prev parent reply other threads:[~2016-09-25 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 7:08 thousands of kworker processes with 4.7.x and 4.8-rc* Tomasz Chmielewski
2016-09-23 13:23 ` Tomasz Chmielewski
2016-09-23 14:10 ` Mike Galbraith
2016-09-23 16:15 ` Tomasz Chmielewski
[not found] ` <a08b61cee6c43de99ac3c6a8cacfdc04@admin.virtall.com>
2016-09-25 12:40 ` Tomasz Chmielewski
2016-09-25 17:21 ` Mike Galbraith
2016-09-25 18:22 ` Mike Galbraith [this message]
2016-09-25 19:07 ` Nikolay Borisov
2016-09-27 3:49 ` Tomasz Chmielewski
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=1474827749.8570.12.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.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.