From: Volker <mail@blafoo.org>
Cc: xfs@oss.sgi.com
Subject: Re: OOM on quotacheck (again?)
Date: Mon, 24 Sep 2012 16:47:25 +0200 [thread overview]
Message-ID: <5060727D.4000009@blafoo.org> (raw)
In-Reply-To: <20120924132113.GL20960@dastard>
Hi,
>> Could you slightly elaborate on that or give me a link or two which
>> explain the matter?
>
> The kernel segment is limited to 960MB of RAM on ia32 bit machines
> unless you build with special config options that allow for up to
> 3GB of kernel memory. The trade off is that you've only got 4GB of
> RAM in teh process address space, so by default you have 3GB of RAM
> for each process (i.e. 960MB/3GB kernel/user split). If you change
> that to a 3GB/1GB split, you'll have problems with applications
> that are memory hogs running out of memory.
Interesting!
> As to the memory used by the inode cache, inodes tend to use between
> 1-1.5k of RAM each. Hence for a 960MB kernel segment, you *might* be
> able to cache 500,000 inodes if you don't cache anything else.
> Typically it will be 25-30% of that number (200-300MB of RAM in
> caching inodes during filesystem traversal). Seeing as you have
> millions of inodes, that's way more than you can cache in available
> kernel memory...
Great! That answered all my questions! Thanks a lot!
3.6.0-rc6-x64 ist currently running fine on 6 machines.
-volker
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-24 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 14:12 OOM on quotacheck (again?) blafoo
2012-09-19 20:59 ` Dave Chinner
2012-09-20 9:32 ` Volker
2012-09-24 13:21 ` Dave Chinner
2012-09-24 14:47 ` Volker [this message]
2012-10-02 16:29 ` Volker
2012-10-02 20:09 ` Dave Chinner
2012-10-02 20:49 ` Volker
2012-10-02 22:15 ` Dave Chinner
2012-10-04 14:19 ` Volker
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=5060727D.4000009@blafoo.org \
--to=mail@blafoo.org \
--cc=xfs@oss.sgi.com \
/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