From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755547AbcI0DuL (ORCPT ); Mon, 26 Sep 2016 23:50:11 -0400 Received: from mail.virtall.com ([178.63.195.102]:56885 "EHLO mail.virtall.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753111AbcI0DuE (ORCPT ); Mon, 26 Sep 2016 23:50:04 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=wpkg.org; h=mime-version :content-type:content-transfer-encoding:date:from:to:cc:subject :in-reply-to:references:message-id; q=dns; s=default; b=I+dHStOQ /16awCy/Zf3p5C+pTq/85PpT3la/RDepDKnNFQTda+bVD2YgeKcpksQNF4NJQQn/ jwzgmaUFRmVB/+y/H4Kxsq1sxhoEd1YA2fB1ZBiuEVZoa/sDCl1rMFf7kIyJoESA QPzvcnElpcVotfnbVFIdq1vdlF132mZ60pY= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 27 Sep 2016 12:49:58 +0900 From: Tomasz Chmielewski To: Nikolay Borisov Cc: Mike Galbraith , LKML Subject: Re: thousands of kworker processes with 4.7.x and 4.8-rc* In-Reply-To: <95eb1349-fcd4-4713-31fc-695c6255ae30@gmail.com> References: <35b2acf87bfeaf1d04f2cf3d10b99b6e@admin.virtall.com> <20acd5801291dff03ed56b63919b9249@admin.virtall.com> <1474639800.4025.29.camel@gmail.com> <50d06a3b797091821d190196b48e8d52@admin.virtall.com> <95eb1349-fcd4-4713-31fc-695c6255ae30@gmail.com> Message-ID: User-Agent: Roundcube Webmail/1.2.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016-09-26 04:07, Nikolay Borisov wrote: >> 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. FYI, it was reproduced and bisected here (scroll to the bottom): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626564 Tomasz Chmielewski https://lxadm.com