From: Cyril Hrubis <chrubis@suse.cz>
To: Li Wang <wangli.ahau@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Fwd: [PATCH] mem/hugeshmat: new case for hugepage leak inspection
Date: Mon, 26 Jan 2015 17:53:59 +0100 [thread overview]
Message-ID: <20150126165359.GC29158@rei> (raw)
In-Reply-To: <CAE1O6mjDP5TJi6XaqaX18VQXTpZFU04ReB250GZWRimjJBkhWA@mail.gmail.com>
Hi!
> Description of Problem:
> When over 1GB shared memory was alocated in hugepage, the hugepage
> is not released though process finished.
>
> Signed-off-by: Li Wang <liwang@redhat.com>
Ah, there is another version. Usually people add version number to the
email subject so that is clear which patch is the newest and include
short list of changes from the previous versions...
Which one is the latest version?
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2015-01-26 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1419737900-6117-1-git-send-email-liwang@redhat.com>
2014-12-28 4:06 ` [LTP] [PATCH] mem/hugeshmat: new case for hugepage leak inspection Li Wang
[not found] ` <197257986.1477814.1419759005661.JavaMail.zimbra@redhat.com>
2014-12-28 9:31 ` [LTP] Fwd: " Li Wang
2015-01-26 16:53 ` Cyril Hrubis [this message]
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=20150126165359.GC29158@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangli.ahau@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