From: "Theodore Ts'o" <tytso@mit.edu>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: util-linux@vger.kernel.org
Subject: Re: fsck memory leak
Date: Fri, 4 Dec 2015 17:17:20 -0500 [thread overview]
Message-ID: <20151204221720.GD18359@thunk.org> (raw)
In-Reply-To: <n3st78$77b$1@ger.gmane.org>
On Fri, Dec 04, 2015 at 09:31:36PM +0100, U.Mutlu wrote:
>
> I think it's a double-edged sword: if user has less memory then
> the integrated caching will IMO degrade the performance.
You're wrong.
> Btw, why does my "free" command not have the "available" column?
> Or did you use a different tool for the above outputs?
Probably because you're using an older version of procps. The
difference is between 2:3.3.9-9 and 2:3.3.10-2 (which recently entered
Debian testing).
The older version of free has a "-/+ buffers/cache" line, and the Free
entry in the "-/+ buffer/cache" line is equivalent to the available
line. So you're version of free looks like this:
total used free shared buffers cached
Mem: 15G 7.1G 8.2G 421M 303M 1.6G
-/+ buffers/cache: 5.2G ===> 10G <===
Swap: 0B 0B 0B
- Ted
;
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe util-linux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-04 22:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-12-04 22:01 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2015-12-04 23:08 Dave Rutherford
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=20151204221720.GD18359@thunk.org \
--to=tytso@mit.edu \
--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