public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>, kanoj@netxen.com
Subject: Re: kswapd busy but not swapping
Date: Wed, 21 May 2008 11:13:37 +0200	[thread overview]
Message-ID: <1211361217.6463.61.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0805210050440.13780@sheep.housecafe.de>

On Wed, 2008-05-21 at 01:04 +0200, Christian Kujau wrote:
> Hi,
> 
> I noticed that the [kswapd0] thread was eating 3-7% cpu time but no 
> swapspace has been used yet. This is with a just booted 2.6.25.4 system,
> currently with some disk i/o going on.
> 
> So I figured that kswapd might not be responsible for "swapping" after 
> all, although the name suggests it. Grep'ing Documentation/ for kswapd did 
> not reveal much. Is the paper from Kanoj[0] still valid for 2.6 kernels? 
> The SGI page referenced in Documentation/kernel-docs.txt is down, but 
> there's a .txt version on [1] which tells me:
> 
>    "When memory runs low, and a process can not find a free page, it wakes
>     up kswapd, the memory stealer"
> 
> So, if I'd run low on memory, kswapd would be active. But I don't see that 
> in free(1):
> 
> # free -m
>               total       used       free     shared    buffers     cached
> Mem:          2023       1662        360          0        820        315
> -/+ buffers/cache:        526       1496
> Swap:         1505          0       1505

It could have been busy reclaiming pagecache.

kswapd is the generic reclaim thread - paging anonymous memory to the
swap is but one form thereof.


  reply	other threads:[~2008-05-21  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 23:04 kswapd busy but not swapping Christian Kujau
2008-05-21  9:13 ` Peter Zijlstra [this message]
2008-05-21 18:42   ` Christian Kujau

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=1211361217.6463.61.camel@lappy.programming.kicks-ass.net \
    --to=a.p.zijlstra@chello.nl \
    --cc=kanoj@netxen.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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