All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Zhouping Liu <zliu@redhat.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH v3 0/3] mm/thp: add two new case
Date: Mon, 15 Apr 2013 15:46:43 +0800	[thread overview]
Message-ID: <516BB063.3060801@cn.fujitsu.com> (raw)
In-Reply-To: <cover.1366005109.git.zliu@redhat.com>

Hi Zhouping:
> The patchset is desinged to test THP functionality.
> 
> when one process allocate hugepage aligned anonymouse 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.

I just see that on the kernel before v2.6.39, the "defrag"
interface is "[yes] no" or "yes [no]"(eg. RHEL6). While it's changed
to boolean after commit e27e6151b154 in v2.6.39-rc4.

So, you should deal with the multi-style interface of this "defrag",

+		SAFE_FILE_SCANF(cleanup, PATH_KHPD "defrag", "%ld", &defrag);

Thanks,
Wanlong Gao

> 
> Wanlong, I included you into 'Tested-by' thread, thanks for
> your reviewing and testing the patchset.
> 
> Zhouping Liu (3):
>   mm/thp: new case thp04.c
>   lib/mem: introduce a new function set_global_mempolicy()
>   mm/thp: add new case thp05
> 
>  runtest/mm                         |   6 ++
>  testcases/kernel/mem/include/mem.h |  12 +++
>  testcases/kernel/mem/lib/mem.c     | 203 ++++++++++++++++++++++++++++++++++++-
>  testcases/kernel/mem/thp/thp04.c   | 136 +++++++++++++++++++++++++
>  testcases/kernel/mem/thp/thp05.c   | 152 +++++++++++++++++++++++++++
>  5 files changed, 508 insertions(+), 1 deletion(-)
>  create mode 100644 testcases/kernel/mem/thp/thp04.c
>  create mode 100644 testcases/kernel/mem/thp/thp05.c
> 


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

  parent reply	other threads:[~2013-04-15  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  5:59 [LTP] [PATCH v3 0/3] mm/thp: add two new case Zhouping Liu
2013-04-15  5:59 ` [LTP] [PATCH v3 1/3] mm/thp: new case thp04.c Zhouping Liu
2013-04-15  5:59 ` [LTP] [PATCH v3 2/3] lib/mem: introduce a new function set_global_mempolicy() Zhouping Liu
2013-04-15  5:59 ` [LTP] [PATCH v3 3/3] mm/thp: add new case thp05 Zhouping Liu
2013-04-15  7:46 ` Wanlong Gao [this message]
2013-04-15  9:26   ` [LTP] [PATCH v3 0/3] mm/thp: add two new case Zhouping Liu
2013-04-15  9:41     ` Wanlong Gao

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=516BB063.3060801@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=zliu@redhat.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 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.