From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] memcg_function:fix the wrong use of mlock
Date: Thu, 15 Dec 2011 13:52:52 +0800 [thread overview]
Message-ID: <4EE98B34.2070709@cn.fujitsu.com> (raw)
In-Reply-To: <CAGH67wQxgxm01PQVGyaMTDgThGU8pNUSMsrAkVMX2MBiAX48JQ@mail.gmail.com>
Hi Garrett:
What do you think about the patch set below now?
[PATCH 0/5] Automatically mount hugetlbfs for hugemmap tests.
Thanks a lot
-Wanlong Gao
> On Wed, Dec 14, 2011 at 7:04 PM, Wanlong Gao <gaowanlong@cn.fujitsu.com> wrote:
>> On 12/15/2011 10:46 AM, Peng Haitao wrote:
>>
>>>
>>> mlock and munmap will return -1 when ERROR.
>>>
>>> Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
>>
>> Reviewed-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
>
> Committed -- thanks!
> -Garrett
>
------------------------------------------------------------------------------
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT complexity
while improving strategic productivity. Learn More!
http://www.accelacomm.com/jaw/sdnl/114/51507609/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2011-12-15 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EE95F75.6030909@cn.fujitsu.com>
2011-12-15 3:05 ` [LTP] [PATCH] memcg_function:fix the wrong use of mlock Caspar Zhang
[not found] ` <4EE963A9.7030100@cn.fujitsu.com>
2011-12-15 5:44 ` Garrett Cooper
2011-12-15 5:52 ` Wanlong Gao [this message]
[not found] ` <6d5f6f84-cdfa-42d0-a3a5-f9d028419818@zmail16.collab.prod.int.phx2.redhat.com>
2011-12-21 14:09 ` Cyril Hrubis
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=4EE98B34.2070709@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.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