From: Zhouping Liu <zliu@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH v5 0/3] mm/thp: add two new case
Date: Tue, 16 Apr 2013 23:52:14 -0400 (EDT) [thread overview]
Message-ID: <580855074.1538065.1366170734748.JavaMail.root@redhat.com> (raw)
In-Reply-To: <516E1673.6090902@cn.fujitsu.com>
----- Original Message -----
> From: "Wanlong Gao" <gaowanlong@cn.fujitsu.com>
> To: "Zhouping Liu" <zliu@redhat.com>
> Cc: "LTP List" <ltp-list@lists.sourceforge.net>
> Sent: Wednesday, April 17, 2013 11:26:43 AM
> Subject: Re: [LTP] [PATCH v5 0/3] mm/thp: add two new case
>
> On 04/16/2013 10:30 PM, Zhouping Liu wrote:
> > The patchset is desinged to test THP functionality.
> >
> > when one process allocate hugepage aligned anonymous pages,
> > kernel thread 'khugepaged' controlled by sysfs knobs
> > /sys/kernel/mm/transparent_hugepage/* will scan them, and make
> > them as transparent hugepage if they are suited, you can find out
> > how many transparent hugepages are there in one process from
> > /proc/<pid>/smaps, among the file contents, 'AnonHugePages' entry
> > stand for transparent hugepage.
> >
> > v1 to v2:
> > accepted Wanlong's suggestion, added some comment for '10s'
> > added 'static' key word for single-file-only variant.
> >
> > v2 to v3:
> > added some comments for low memory system.
> >
> > v3 to v4:
> > Wanglong point out that the value of khugepaged/defrag is string type,
> > not a numeric before applying the commit e27e6151b154 in v2.6.39-rc4,
> > and I checked the code again, found the current cases thp0* don't be
> > effected by khugepaged/defrag, so I removed the checking of
> > khugepaged/defrag from khugepaged_scan_done().
> >
> > v4 to v5:
> > 1. made some cleaup
> > 2. updated 10s to 5s for each checking in khugepaged_scan_done()
> > 3. used SAFE_FILE_SCANF|PRINTF() instead of write_file()
> >
> > v5 to v6:
> > made a little cleanup.
>
> Applied this V6, thank you.
>
> You may use the wrong --subject-prefix
yeah, thanks for your friendly correcting, I used the history command :(
--
Thanks,
Zhouping
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-04-17 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 14:30 [LTP] [PATCH v5 0/3] mm/thp: add two new case Zhouping Liu
2013-04-16 14:30 ` [LTP] [PATCH v4 1/3] mm/thp: new case thp04.c Zhouping Liu
2013-04-16 14:30 ` [LTP] [PATCH v4 2/3] lib/mem: introduce a new function set_global_mempolicy() Zhouping Liu
2013-04-16 14:30 ` [LTP] [PATCH v4 3/3] mm/thp: add new case thp05 Zhouping Liu
2013-04-17 3:26 ` [LTP] [PATCH v5 0/3] mm/thp: add two new case Wanlong Gao
2013-04-17 3:52 ` Zhouping Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-16 10:26 Zhouping Liu
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=580855074.1538065.1366170734748.JavaMail.root@redhat.com \
--to=zliu@redhat.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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