All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xishi Qiu <qiuxishi@huawei.com>
To: "Daniel K." <dk@syse.no>
Cc: 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: Sat, 6 Feb 2016 09:19:40 +0800	[thread overview]
Message-ID: <56B54A2C.5010407@huawei.com> (raw)
In-Reply-To: <56B48B2D.4020502@syse.no>

On 2016/2/5 19:44, Daniel K. wrote:

> 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?
> 

Hi Daniel,

No, I mean "Cached: 3727824 kB" and "buff/cache 6062M" are different.

Does "buff/cache" include Buffers, Cached, and Slab?

Thanks,
Xishi Qiu

> 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>

WARNING: multiple messages have this Message-ID (diff)
From: Xishi Qiu <qiuxishi@huawei.com>
To: "Daniel K." <dk@syse.no>
Cc: 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: Sat, 6 Feb 2016 09:19:40 +0800	[thread overview]
Message-ID: <56B54A2C.5010407@huawei.com> (raw)
In-Reply-To: <56B48B2D.4020502@syse.no>

On 2016/2/5 19:44, Daniel K. wrote:

> 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?
> 

Hi Daniel,

No, I mean "Cached: 3727824 kB" and "buff/cache 6062M" are different.

Does "buff/cache" include Buffers, Cached, and Slab?

Thanks,
Xishi Qiu

> Drop the -m switch to free.
> 
> Also, give 'man free' a spin, it explains what's behind the numbers.
> 
> 
> Daniel K.
> 
> .
> 

  reply	other threads:[~2016-02-06  1:23 UTC|newest]

Thread overview: 6+ 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  7:50 ` Xishi Qiu
2016-02-05 11:44 ` Daniel K.
2016-02-05 11:44   ` Daniel K.
2016-02-06  1:19   ` Xishi Qiu [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=56B54A2C.5010407@huawei.com \
    --to=qiuxishi@huawei.com \
    --cc=dk@syse.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.