public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: excessive kworker activity when idle. (was Re: vma corruption in today's -git)
Date: Thu, 31 Mar 2011 00:08:18 -0400	[thread overview]
Message-ID: <20110331040818.GB1255@redhat.com> (raw)
In-Reply-To: <AANLkTimPi-Vbi3DNLEeShCpfOJEuUZo3--3CQ_BMgJiS@mail.gmail.com>

On Wed, Mar 30, 2011 at 08:44:06PM -0700, Linus Torvalds wrote:
 
 > So clearly there are shmem inodes being destroyed, but it shouldn't be
 > from an hour ago. I wonder if your system isn't as idle as you think
 > it is.

hmm. when I say idle, I mean  I'm staring at a gnome-terminal with
and ssh client, and nothing else.  Certainly nothing that should be
causing the cpu meter in the taskbar to almost max out, and definitely
nothing that should cause the fans in the laptop to be roaring.

If you want to try and repeat this experiment, this should do it..

git clone git://git.codemonkey.org.uk/trinity
cd trinity ; make
./trinity --mode=random -i

let it run for a while, then kill it.   kworker should then go nuts.

	Dave


  reply	other threads:[~2011-03-31  4:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  4:09 vma corruption in today's -git Dave Jones
2011-03-29  4:19 ` Américo Wang
2011-03-29  4:26   ` Dave Jones
2011-03-29  4:22 ` Linus Torvalds
2011-03-31  3:09   ` excessive kworker activity when idle. (was Re: vma corruption in today's -git) Dave Jones
2011-03-31  3:34     ` Dave Jones
2011-03-31  3:44       ` Linus Torvalds
2011-03-31  4:08         ` Dave Jones [this message]
2011-03-31 15:53           ` Linus Torvalds
2011-03-31 16:21             ` Linus Torvalds
2011-03-31 21:38               ` Linus Torvalds
2011-03-31 14:59         ` Paul E. McKenney
2011-03-31  3:37     ` Linus Torvalds
2011-03-31  3:55       ` Dave Jones
2011-03-31  5:32         ` Linus Torvalds
2011-03-31 14:21           ` Arnaldo Carvalho de Melo
2011-03-31 14:58           ` Dave Jones
2011-03-31 15:03             ` Dave Jones
2011-03-31 15:09               ` Dave Jones
2011-03-31 15:45                 ` Linus Torvalds
2011-03-31 15:25               ` Linus Torvalds
2011-03-31 15:49                 ` Dave Jones
2011-03-31 15:58                   ` Linus Torvalds
2011-03-31 16:13                     ` Dave Jones
2011-03-31  6:56       ` Tejun Heo
2011-03-31 10:37         ` [PATCH] workqueue: document debugging tricks Florian Mickler
2011-03-31 11:41           ` Tejun Heo

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=20110331040818.GB1255@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox