public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, fabbione@ubuntu.com
Subject: Re: VFS nr_files accounting
Date: Sat, 4 Mar 2006 19:47:17 +0530	[thread overview]
Message-ID: <20060304141717.GA456@in.ibm.com> (raw)
In-Reply-To: <20060304.022546.85833873.davem@davemloft.net>

On Sat, Mar 04, 2006 at 02:25:46AM -0800, David S. Miller wrote:
> 
> I just wanted to report that I am hitting the "VFS: file-max limit xxx
> reached" problem quite easily on my 32-cpu Niagara machine with 16GB
> of ram with current 2.6.x GIT.
> 
> It seems far too easy to get a box into this state due to SLAB
> fragmentation and RCU.  And once you get a machine into this state it
> is totally unusable.
> 
> Our test case is usually a "make -j8192" kernel build along with a
> parallel bootstrap of gcc.  That puts about 256 processes on each
> cpu's runqueue, I doubt ksoftirqd can run much at all.

Dave, there is a set of patches in -mm that may handle this
better -

http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc5/2.6.16-rc5-mm2/broken-out/rcu-batch-tuning.patch
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc5/2.6.16-rc5-mm2/broken-out/fix-file-counting.patch
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc5/2.6.16-rc5-mm2/broken-out/fix-file-counting-fixes.patch

Could you please try this in your setup ?

The rcu-batch tuning patch provides automatic switching to
process as many RCUs as possible if too many of them are queued.
The file counting fixes count the file structures correctly.

Thanks
Dipankar

  reply	other threads:[~2006-03-04 14:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-04 10:25 VFS nr_files accounting David S. Miller
2006-03-04 14:17 ` Dipankar Sarma [this message]
2006-03-04 22:22   ` David S. Miller
2006-03-04 22:28     ` David S. Miller
2006-03-04 22:32       ` David S. Miller
2006-03-05  7:05         ` Dipankar Sarma
2006-03-05  7:37           ` David S. Miller
2006-03-05 11:38             ` Dipankar Sarma
2006-03-06 20:39               ` David S. Miller
2006-03-07  6:41                 ` Dipankar Sarma
2006-03-07  6:47                   ` David S. Miller
2006-03-07  8:02                     ` Dipankar Sarma
2006-03-07  6:53                   ` Nick Piggin
2006-03-07  7:00                     ` David S. Miller
2006-03-07  8:09                       ` Dipankar Sarma
2006-03-07  8:55                         ` Fabio Massimo Di Nitto
2006-03-07  7:06                   ` Andrew Morton
2006-03-07 12:09                     ` Dipankar Sarma

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=20060304141717.GA456@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=davem@davemloft.net \
    --cc=fabbione@ubuntu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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