mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>,
	Mike Galbraith <umgwanakikbuti@gmail.com>
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 22:07:52 +0300	[thread overview]
Message-ID: <95eb1349-fcd4-4713-31fc-695c6255ae30@gmail.com> (raw)
In-Reply-To: <b3cc8ad938677b304b19fdee1e2612e2@admin.virtall.com>



On 25.09.2016 15:40, Tomasz Chmielewski wrote:
> On 2016-09-25 18:29, Tomasz Chmielewski wrote:
> 
>>> I'll try to bisect.
>>
>> OK, not a kernel regression, but some config change caused it.
>> However, I'm not able to locate which change exactly.
>>
>> I'm attaching two configs which I've tried with 4.7.3 - one results in
>> thousands of kworkers, and the other doesn't. Also included a diff
>> between them.
>>
>> Any obvious changes I should try?
> 
> 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.


Why don't you sample the stacks of some of those kworker processes to
see if they are all executing a parituclar piece of work. That might
help you narrow down where they originate from. Cat multiple
/proc/$kworker-pid/stack files and see if a pattern emerges.

Regards,
Nikolay

> 
> 
> Tomasz Chmielewski
> https://lxadm.com
> 
> 

  parent reply	other threads:[~2016-09-25 19:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  7:08 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
2016-09-25 19:07           ` Nikolay Borisov [this message]
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=95eb1349-fcd4-4713-31fc-695c6255ae30@gmail.com \
    --to=n.borisov.lkml@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    --cc=umgwanakikbuti@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome