public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Thorlton <athorlton@sgi.com>
To: athorlton@sgi.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Bob Liu <lliubbo@gmail.com>, David Rientjes <rientjes@google.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Hugh Dickins <hughd@google.com>, Ingo Molnar <mingo@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Mel Gorman <mgorman@suse.de>, Oleg Nesterov <oleg@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vladimir Davydov <vdavydov@parallels.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Convert khugepaged to a task_work function
Date: Wed, 22 Oct 2014 21:43:08 -0500	[thread overview]
Message-ID: <20141023024308.GA14217@sgi.com> (raw)
In-Reply-To: <1414031706-101613-1-git-send-email-athorlton@sgi.com>

Please ignore!  Screwed up my git send-email...  Sending the proper
version here in a bit...

On Wed, Oct 22, 2014 at 09:35:02PM -0500, Alex Thorlton wrote:
> Hey everyone,
> 
> Last week, while discussing possible fixes for some unexpected/unwanted behavior
> from khugepaged (see: https://lkml.org/lkml/2014/10/8/515) several people
> mentioned possibly changing changing khugepaged to work as a task_work function
> instead of a kernel thread.  This will give us finer grained control over the
> page collapse scans, eliminate some unnecessary scans since tasks that are
> relatively inactive will not be scanned often, and eliminate the unwanted
> behavior described in the email thread I mentioned.
> 
> This initial patch is fully functional, but there are quite a few areas that
> will need to be polished up before it's ready to be considered for a merge.  I
> wanted to get this initial version out with some basic test results quickly, so
> that people can give their opinions and let me know if there's anything they'd
> like to see done differently (and there probably is :).  I'll give details on
> the code in the individual patches.
> 
> I gathered some pretty rudimentary test data using a 48-thread NAMD simulation
> pinned to a cpuset with 8 cpus and about 60g of memory.  I'm checking to see if
> I'm allowed to publish the input data so that others can replicate the test.  In
> the meantime, if somebody knows of a publicly available benchmark that stresses
> khugepaged, that would be helpful.
> 
> The only data point I gathered was the number of pages collapsed, sampled every
> ten seconds, for the lifetime of the job.  This one statistic gives a pretty
> decent illustration of the difference in behavior between the two kernels, but I
> intend to add some other counters to measure fully completed scans, failed
> allocations, and possibly scans skipped due to timer constraints.
> 
> The data for the standard kernel (with a very small patch to add the stat
> counter that I used to the task_struct) is available here:
> 
> http://oss.sgi.com/projects/memtests/pgcollapse/output-khpd
> 
> This was a fairly recent kernel (last Tuesday).  Commit ID:
> 2d65a9f48fcdf7866aab6457bc707ca233e0c791.  I'll send the patches I used for that
> kernel as a reply to this message shortly.
> 
> The output from the modified kernel is stored here:
> 
> http://oss.sgi.com/projects/memtests/pgcollapse/output-pgcollapse
> 
> The output is stored in a pretty dumb format (*really* wide).  Best viewed in a
> simple text editor with word wrap off, just fyi.
> 
> Quick summary of what I found:  Both kernels performed about the same when it
> comes to overall runtime, my kernel was 22 seconds faster with a total runtime
> of 4:13:07.  Not a significant difference, but important to note that there was
> no apparent performance degradation.  The most interesting result is that my
> kernel completed the majority of the necessary page collapses for this job in
> 2:04, whereas the mainline kernel took 29:05 to get to the same point.
> 
> Let me know what you think.  Any suggestions are appreciated!
> 
> - Alex
> 
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Bob Liu <lliubbo@gmail.com>
> Cc: David Rientjes <rientjes@google.com>
> Cc: Eric W. Biederman <ebiederm@xmission.com>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Mel Gorman <mgorman@suse.de>
> Cc: Oleg Nesterov <oleg@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Rik van Riel <riel@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Vladimir Davydov <vdavydov@parallels.com>
> Cc: linux-kernel@vger.kernel.org
> 
> Alex Thorlton (4):
>   Disable khugepaged thread
>   Add pgcollapse controls to task_struct
>   Convert khugepaged scan functions to work with task_work
>   Add /proc files to expose per-mm pgcollapse stats
> 
>  fs/proc/base.c             |  23 +++++++
>  include/linux/khugepaged.h |  10 ++-
>  include/linux/sched.h      |  16 +++++
>  kernel/fork.c              |   7 ++
>  kernel/sched/fair.c        |  18 +++++
>  mm/huge_memory.c           | 162 +++++++++++++++------------------------------
>  6 files changed, 123 insertions(+), 113 deletions(-)
> 
> -- 
> 1.7.12.4
> 

  reply	other threads:[~2014-10-23  2:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23  2:35 [PATCH 0/4] Convert khugepaged to a task_work function Alex Thorlton
2014-10-23  2:43 ` Alex Thorlton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-23  2:49 Alex Thorlton
2014-10-23 17:55 ` Rik van Riel
2014-10-23 18:05   ` Alex Thorlton
2014-10-23 18:52     ` Alex Thorlton
2014-10-28 12:12 ` Andi Kleen
2014-10-28 12:58   ` Rik van Riel
2014-10-28 15:39     ` Rik van Riel
2014-10-31 20:27       ` Vlastimil Babka
2014-11-17 21:34         ` Alex Thorlton
2014-11-10 11:03     ` Mel Gorman
2014-11-17 21:16       ` Alex Thorlton
2014-10-29 21:58   ` Alex Thorlton
2014-10-30  0:23     ` Kirill A. Shutemov
2014-10-30  8:35     ` Andi Kleen
2014-10-30 18:25       ` Alex Thorlton

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=20141023024308.GA14217@sgi.com \
    --to=athorlton@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hughd@google.com \
    --cc=keescook@chromium.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lliubbo@gmail.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=vdavydov@parallels.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