From: "Nikita V. Youshchenko" <yoush@cs.msu.su>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange situation while writing CDR from iso file on tmpfs
Date: Wed, 3 Sep 2003 22:54:50 +0400 [thread overview]
Message-ID: <200309032254.50468@sercond.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0309031745110.2222-100000@localhost.localdomain>
> tmpfs is fine while everything is in memory, and even when a little
> overflowed to swap; but with so much on swap it's at the mercy of the
> vagaries of the LRU lists, and swap allocation might work out far
> from optimal for it. tmpfs use of swap is not something we've ever
> tried to optimize for.
Hmm...
Until today I thought that it is a good administration style to create a
several gigabyte swap partition (which is normally almost unused, but
just for the case that some program needs much virtual memory), and use
tmpfs for /tmp.
I thought that it is good for two reasons - disk space is not wasted for
/tmp (and /tmp still has several gigabytes of space), and short-living
temporary files such as gcc intermediate files normally reside in memory,
which is more effective than using a filesystem on a disk.
If I understand you correctly, the above is not true at least for a
desktop system with 256M of RAM?
And what about LTSP server with 2 gigabytes of RAM (and 6 gigabytes of
swap) that normally runs 10-15 KDE sessions with mozilla's and
openoffice's?
> Perhaps something exceptionally stupid and avoidable occurs, I'll keep
> your mail as reminder to investigate some day.
Thank you.
next prev parent reply other threads:[~2003-09-03 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 21:20 Nikita V. Youshchenko
2003-09-03 17:18 ` Hugh Dickins
2003-09-03 18:54 ` Nikita V. Youshchenko [this message]
2003-09-03 19:14 ` Hugh Dickins
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=200309032254.50468@sercond.localdomain \
--to=yoush@cs.msu.su \
--cc=hugh@veritas.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
all inboxes | Powered by JetHome®