From: Caspar Zhang <caspar@casparzhang.com>
To: Peng Haitao <penght@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] memcg_move_charge_at_immigrate_test: fix a bug of usage_in_bytes is not 'exact'
Date: Wed, 25 Apr 2012 11:34:23 +0800 [thread overview]
Message-ID: <4F9770BF.5050609@casparzhang.com> (raw)
In-Reply-To: <4F977041.9070607@casparzhang.com>
On 04/25/2012 11:32 AM, Caspar Zhang wrote:
> On 04/25/2012 11:06 AM, Wanlong Gao wrote:
>> On 04/24/2012 03:43 PM, Peng Haitao wrote:
>>
>>> In memory.txt says:
>>> usage_in_bytes is affected by the method and doesn't show 'exact' value of memory(and swap) usage, it's an fuzz value for efficient access. (Of course, when necessary, it's synchronized.) If you want to know more exact memory usage, you should use RSS+CACHE(+SWAP) value in memory.stat(see 5.2).
>>>
>>> So memory.usage_in_bytes should be replaced with memory.stat in the case of
>>> memcg_move_charge_at_immigrate_test.
>
> Hi, Please break your commit message into <= 73 words per line (except
sorry, s/words/characters...
> some running output) next time.
>
> Thanks,
> Caspar
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-04-25 3:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 7:43 [LTP] [PATCH] memcg_move_charge_at_immigrate_test: fix a bug of usage_in_bytes is not 'exact' Peng Haitao
2012-04-25 3:06 ` Wanlong Gao
2012-04-25 3:32 ` Caspar Zhang
2012-04-25 3:34 ` Caspar Zhang [this message]
2012-04-25 3:39 ` Peng Haitao
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=4F9770BF.5050609@casparzhang.com \
--to=caspar@casparzhang.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=penght@cn.fujitsu.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