From: Dave Rutherford <dave@evilpettingzoo.com>
To: util-linux@vger.kernel.org
Cc: "U.Mutlu" <for-gmane@mutluit.com>
Subject: Re: fsck memory leak
Date: Fri, 4 Dec 2015 18:08:14 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1512041806510.17213@bb> (raw)
On Fri, Dec 4, 2015 at 5:26 PM, U.Mutlu <for-gmane@mutluit.com> wrote:
> I'm not a friend of such default integrated system caching, it reminds
> me of Windows idiocy. This is nothing but a diskcache in ram,
... made up strictly of memory that nothing else wants.
This is different than a ramdisk, which itself is something that wants
RAM.
> but then
> the admin should have the the freedom to set the size of the cache via
> a config file in etc, for example /etc/default/cache or in
/etc/default/tmpfs.
Why? It's memory that *nothing else wants*. It's given up instantly
the moment something else needs to use it. So there's no downside,
unlike with that other "operating system" you mention.
> :-)
:-(
--
Prius I, Pontiff, Schenectadian Catholic Church
next reply other threads:[~2015-12-04 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 23:08 Dave Rutherford [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-04 7:15 fsck memory leak U.Mutlu
2015-12-04 7:49 ` U.Mutlu
2015-12-04 10:21 ` Karel Zak
2015-12-04 18:00 ` U.Mutlu
2015-12-04 15:19 ` Theodore Ts'o
2015-12-04 17:53 ` U.Mutlu
2015-12-04 19:09 ` U.Mutlu
2015-12-04 19:58 ` Theodore Ts'o
2015-12-04 20:31 ` U.Mutlu
2015-12-04 21:40 ` Ruediger Meier
2015-12-04 22:26 ` U.Mutlu
2015-12-04 22:03 ` Mike Frysinger
2015-12-04 22:17 ` Theodore Ts'o
2015-12-04 22:01 ` Mike Frysinger
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=alpine.DEB.2.02.1512041806510.17213@bb \
--to=dave@evilpettingzoo.com \
--cc=for-gmane@mutluit.com \
--cc=util-linux@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