LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>,
Mika Lawando <rzryyvzy@trashmail.net>
Subject: Re: What is the limit size of tmpfs /dev/shm ?
Date: Wed, 6 Feb 2008 19:48:22 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0802061938120.32204@blonde.site> (raw)
In-Reply-To: <47AA0A2E.30701@zytor.com>
On Wed, 6 Feb 2008, H. Peter Anvin wrote:
> Hugh Dickins wrote:
> >
> > Don't forget that tmpfs overflows into swap, so you could save money
> > by adding adding more swap and cutting down on the RAM: though of
> > course that will perform very poorly once it's actually using the
> > swap, probably not the direction you want to go in.
>
> It can still outperform conventional disk filesystems, however, mostly because
> it doesn't have to worry one iota about consistency.
In theory, yes, and should be true in practice before it hits swap.
But I think you'll find our swap handling is too primitive for tmpfs
to perform well once we hit swap. Most filesystems pay considerable
attention to good performance within their constraints of correctness.
Whereas with tmpfs we've just never worried about the performance once
swapping. It's used so you don't lose your data, but if you're really
expecting to be going to disk very much, better start with a filesystem
really designed for that.
Hugh
next prev parent reply other threads:[~2008-02-06 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 14:54 Tomasz Chmielewski
2008-02-06 15:06 ` rzryyvzy
2008-02-06 15:29 ` Hugh Dickins
2008-02-06 19:27 ` H. Peter Anvin
2008-02-06 19:48 ` Hugh Dickins [this message]
2008-02-06 19:53 ` H. Peter Anvin
2008-02-06 21:58 ` Hugh Dickins
2008-02-06 22:01 ` H. Peter Anvin
2008-02-06 22:40 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2008-02-06 13:54 Mika Lawando
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=Pine.LNX.4.64.0802061938120.32204@blonde.site \
--to=hugh@veritas.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=rzryyvzy@trashmail.net \
--subject='Re: What is the limit size of tmpfs /dev/shm ?' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).