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: [PATCH 0/1] mm, shmem: map few pages around fault address if they are in page cache
Date: Fri, 28 Feb 2014 14:18:50 -0800 [thread overview]
Message-ID: <1393625931-2858-1-git-send-email-quning@google.com> (raw)
This is a follow-up patch for "mm: map few pages around fault address if they are in page cache"
We use the generic filemap_map_pages as ->map_pages in shmem/tmpfs.
Please consider applying.
=========================================================================
Below is just some simple experiment numbers from this patch, let me know if
you would like more:
Tested on Xeon machine with 64GiB of RAM, using the current default fault
order 4.
Sequential access 8GiB file
Baseline with-patch
1 thread
minor fault 205 101
time, seconds 7.94 7.82
Random access 8GiB file
Baseline with-patch
1 thread
minor fault 724 623
time, seconds 9.75 9.84
Ning Qu (1):
mm: implement ->map_pages for shmem/tmpfs
mm/shmem.c | 1 +
1 file changed, 1 insertion(+)
--
1.9.0.279.gdc9e3eb
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
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: [PATCH 0/1] mm, shmem: map few pages around fault address if they are in page cache
Date: Fri, 28 Feb 2014 14:18:50 -0800 [thread overview]
Message-ID: <1393625931-2858-1-git-send-email-quning@google.com> (raw)
This is a follow-up patch for "mm: map few pages around fault address if they are in page cache"
We use the generic filemap_map_pages as ->map_pages in shmem/tmpfs.
Please consider applying.
=========================================================================
Below is just some simple experiment numbers from this patch, let me know if
you would like more:
Tested on Xeon machine with 64GiB of RAM, using the current default fault
order 4.
Sequential access 8GiB file
Baseline with-patch
1 thread
minor fault 205 101
time, seconds 7.94 7.82
Random access 8GiB file
Baseline with-patch
1 thread
minor fault 724 623
time, seconds 9.75 9.84
Ning Qu (1):
mm: implement ->map_pages for shmem/tmpfs
mm/shmem.c | 1 +
1 file changed, 1 insertion(+)
--
1.9.0.279.gdc9e3eb
next reply other threads:[~2014-02-28 22:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 22:18 Ning Qu [this message]
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-02-28 22:18 ` Ning Qu
2014-03-01 1:20 ` Hugh Dickins
2014-03-01 1:20 ` Hugh Dickins
2014-03-01 6:36 ` Ning Qu
2014-03-01 6:36 ` Ning Qu
2014-03-03 11:07 ` Kirill A. Shutemov
2014-03-03 11:07 ` Kirill A. Shutemov
2014-03-03 11:07 ` Kirill A. Shutemov
2014-03-03 18:49 ` Ning Qu
2014-03-03 18:49 ` Ning Qu
2014-03-04 20:02 ` Hugh Dickins
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:34 ` Andrew Morton
2014-02-28 22:35 ` Ning Qu
2014-03-01 0:35 ` Ning Qu
2014-03-01 0:35 ` Ning Qu
2014-03-01 1:41 ` Andrew Morton
2014-03-01 1:41 ` Andrew Morton
2014-03-01 6:10 ` Ning Qu
2014-03-01 6:10 ` Ning Qu
2014-03-01 6:27 ` 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:07 ` Ning Qu
2014-03-03 23:29 ` Linus Torvalds
2014-03-03 23:29 ` Linus Torvalds
2014-03-03 23:37 ` Andrew Morton
2014-03-04 0:50 ` Kirill A. Shutemov
2014-03-04 0:50 ` Kirill A. Shutemov
2014-03-05 22:20 ` Ning Qu
2014-03-13 20:46 ` Ning Qu
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=1393625931-2858-1-git-send-email-quning@google.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 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.