public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "bc Wong (chimwong)" <bcwong@cisco.com>
To: linux-kernel@vger.kernel.org
Subject: filp usage when cpu busy
Date: Wed, 31 Oct 2007 18:56:24 -0700	[thread overview]
Message-ID: <47293248.9000906@cisco.com> (raw)

Hi,

With 2.6.16 x86_64 on a 4 core machine, I noticed
that the filp usage (according to /proc/slabinfo)
shoots up and keeps on increasing sharply when one
of the CPUs is (1) locked up, or (2) very busy
doing a lot of printk()'s with KERN_EMERG.

In the case of (1), it's permanent until it runs
out of memory eventually. For (2), it's temporary;
filp count comes back down when the printk()'s are
done.

I can't think of any relationship between a busy/
locked-up CPU and filp count. The system is still
functional. New short-lived processes kept being
created, but the overall number of processes is
stable.

Does anyone know why filp count would go up like
that?

Thanks,
bc

             reply	other threads:[~2007-11-01  1:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  1:56 bc Wong (chimwong) [this message]
2007-11-01  4:05 ` filp usage when cpu busy Nick Piggin
2007-11-01 17:51   ` bc Wong

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=47293248.9000906@cisco.com \
    --to=bcwong@cisco.com \
    --cc=linux-kernel@vger.kernel.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