From: "Daniel K." <dk@syse.no>
To: Xishi Qiu <qiuxishi@huawei.com>, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] why the amount of cache from "free -m" and /proc/meminfo are different?
Date: Fri, 5 Feb 2016 11:44:45 +0000 [thread overview]
Message-ID: <56B48B2D.4020502@syse.no> (raw)
In-Reply-To: <56B45457.4010702@huawei.com>
On 02/05/2016 07:50 AM, Xishi Qiu wrote:
> [root@localhost ~]# free -m
> total used free shared buff/cache available
> Mem: 48295 574 41658 8 6062 46344
> Swap: 24191 0 24191
>
> [root@localhost ~]# cat /proc/meminfo
> Buffers: 0 kB
> Cached: 3727824 kB
> Slab: 2480092 kB
free and meminfo seems to match up pretty well to me.
Are you really asking about display in MB vs kB?
Drop the -m switch to free.
Also, give 'man free' a spin, it explains what's behind the numbers.
Daniel K.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-02-05 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 7:50 [RFC] why the amount of cache from "free -m" and /proc/meminfo are different? Xishi Qiu
2016-02-05 11:44 ` Daniel K. [this message]
2016-02-06 1:19 ` Xishi Qiu
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=56B48B2D.4020502@syse.no \
--to=dk@syse.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.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;
as well as URLs for NNTP newsgroup(s).