From: Ning Qu <quning@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Matthew Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Dave Chinner <david@fromorbit.com>, Ning Qu <quning@gmail.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Ning Qu <quning@google.com>
Subject: Re: [PATCH 0/1] mm, shmem: map few pages around fault address if they are in page cache
Date: Wed, 5 Mar 2014 14:20:41 -0800 [thread overview]
Message-ID: <CACz4_2eYUOkHdOtBJGDGMMwBcQkyPs8BDXQ491Ab_ig4z8q5mQ@mail.gmail.com> (raw)
In-Reply-To: <1393625931-2858-1-git-send-email-quning@google.com>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
Sorry for the delay, here comes the new results from usemem which Kirill
used in the previous patch.
Tested on Xeon machine with 64GiB of RAM, using the current default fault order
4.
Sequential access 16GiB file
Baseline with-patch
1 thread
minor fault 4,194,406 262,194
time, seconds 6.38 5.08
8 thread
minor fault 33,554,768 3,466,150
time, seconds 10.92 7.33
32 thread
minor fault 134,220,140 8,450,265
time, seconds 40.77 34.24
60 thread
minor fault 251,661,943 15,790,478
time, seconds 77.23 65.19
120 thread
minor fault 503,330,421 31,578,717
time, seconds 143.11 130.58
Random access 16GiB file
Baseline with-patch
1 thread
minor fault 263,568 16,667
time, seconds 10.08 10.57
8 thread
minor fault 2,097,700 184,134
time, seconds 13.65 13.66
32 thread
minor fault 8,389,948 579,089
time, seconds 39.44 38.56
60 thread
minor fault 15,733,099 1,019,478
time, seconds 73.67 72.63
120 thread
minor fault 31,467,940 2,009,898
time, seconds 148.48 145.81
[-- Attachment #2: Type: text/html, Size: 6608 bytes --]
next prev parent reply other threads:[~2014-03-05 22:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 22:18 [PATCH 0/1] mm, shmem: map few pages around fault address if they are in page cache Ning Qu
2014-02-28 22:18 ` [PATCH 1/1] mm: implement ->map_pages for shmem/tmpfs Ning Qu
2014-03-01 1:20 ` Hugh Dickins
2014-03-01 6:36 ` Ning Qu
2014-03-03 11:07 ` Kirill A. Shutemov
2014-03-03 18:49 ` Ning Qu
2014-03-04 20:02 ` Hugh Dickins
2014-02-28 22:34 ` [PATCH 0/1] mm, shmem: map few pages around fault address if they are in page cache Andrew Morton
2014-02-28 22:35 ` Ning Qu
2014-03-01 0:35 ` Ning Qu
2014-03-01 1:41 ` Andrew Morton
2014-03-01 6:10 ` Ning Qu
2014-03-01 6:27 ` Ning Qu
2014-03-03 22:38 ` Andrew Morton
2014-03-03 23:07 ` Ning Qu
2014-03-03 23:29 ` Linus Torvalds
2014-03-03 23:37 ` Andrew Morton
2014-03-04 0:50 ` Kirill A. Shutemov
2014-03-05 22:20 ` Ning Qu [this message]
2014-03-13 20:46 ` Ning Qu
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=CACz4_2eYUOkHdOtBJGDGMMwBcQkyPs8BDXQ491Ab_ig4z8q5mQ@mail.gmail.com \
--to=quning@google.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=david@fromorbit.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=mgorman@suse.de \
--cc=quning@gmail.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).