From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
cl@linux-foundation.org,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mingo@elte.hu" <mingo@elte.hu>,
andi@firstfloor.org, minchan.kim@gmail.com
Subject: [mm][RFC][PATCH 0/11] mm accessor updates.
Date: Wed, 16 Dec 2009 12:00:11 +0900 [thread overview]
Message-ID: <20091216120011.3eecfe79.kamezawa.hiroyu@jp.fujitsu.com> (raw)
This is from Christoph Lameter's mm_accessor patch posted 5/Nov.
Replacing all access to mm->mmap_sem with mm-accessor functions as
mm_read_lock,
mm_write_lock,
etc...
This kind of function allows us to improve page fault performance etc..
For example, skil down_read(mmap_sem) in some situation.
(as: http://marc.info/?l=linux-mm&m=125809791306459&w=2)
Because I like this idea, I updated his patch. But the size of patch is
very big and mmap_sem is used in many place, some senario for merging
will be required. Spliting into small pieace and go ahead in step by step.
My plan is...
1. leave mm->mmap_sem as it is for a while.
2. replace all mmap_sem access under /kernel /mm /fs etc..
3. replace all mmap_sem callers under /driver
4. And finally, post per-arch patches.
Now this set is organized as
[1/11] mm_accessor definition
[2/11] a patch for kernel, mm
[3/11] a patch for fs (procfs and codes around get_user_page())
[4/11] a patch for kvm
[5/11] a patch for tomoyo
[6/11] a patch for driver/gpu
[7/11] a patch for infiniband
[8/11] a patch for driver/media/video
[9/11] a patch for sgi gru
[10/11] a patch for misc drivers
[11/11] a patch for x86.
I think, once I push [1/11] (and 2/11]), I can update other calls in each tree.
And finally successfully rename mm->mmap_sem to some other name.
Any comment is welcome.
Thanks,
-Kame
--
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>
next reply other threads:[~2009-12-16 3:03 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 3:00 KAMEZAWA Hiroyuki [this message]
2009-12-16 3:01 ` [mm][RFC][PATCH 1/11] mm accessor for replacing mmap_sem KAMEZAWA Hiroyuki
2009-12-16 3:02 ` [mm][RFC][PATCH 2/11] mm accessor for kernel core KAMEZAWA Hiroyuki
2009-12-16 3:03 ` [mm][RFC][PATCH 3/11] mm accessor for fs KAMEZAWA Hiroyuki
2009-12-16 3:04 ` [mm][RFC][PATCH 4/11] mm accessor for kvm KAMEZAWA Hiroyuki
2009-12-16 3:05 ` [mm][RFC][PATCH 5/11] mm accessor for tomoyo KAMEZAWA Hiroyuki
2009-12-16 3:06 ` [mm][RFC][PATCH 6/11] mm accessor for driver/gpu KAMEZAWA Hiroyuki
2009-12-16 3:07 ` [mm][RFC][PATCH 7/11] mm accessor for inifiniband KAMEZAWA Hiroyuki
2009-12-16 3:08 ` [mm][RFC][PATCH 8/11] mm accessor for video KAMEZAWA Hiroyuki
2009-12-16 3:09 ` [mm][RFC][PATCH 9/11] mm accessor for sgi gru KAMEZAWA Hiroyuki
2009-12-16 3:10 ` [mm][RFC][PATCH 10/11] mm accessor for misc drivers KAMEZAWA Hiroyuki
2009-12-16 3:11 ` [mm][RFC][PATCH 11/11] mm accessor for x86 KAMEZAWA Hiroyuki
2009-12-16 10:11 ` [mm][RFC][PATCH 0/11] mm accessor updates Andi Kleen
2009-12-16 10:13 ` KAMEZAWA Hiroyuki
2009-12-16 10:28 ` Andi Kleen
2009-12-16 10:31 ` KAMEZAWA Hiroyuki
2009-12-16 10:49 ` Andi Kleen
2009-12-16 11:12 ` KAMEZAWA Hiroyuki
2009-12-16 11:31 ` Andi Kleen
2009-12-16 16:27 ` Christoph Lameter
2009-12-16 23:01 ` Peter Zijlstra
2009-12-17 4:11 ` KOSAKI Motohiro
2009-12-17 8:41 ` Andi Kleen
2009-12-16 22:57 ` Peter Zijlstra
2009-12-17 8:40 ` Andi Kleen
2009-12-17 8:45 ` Peter Zijlstra
2009-12-17 8:54 ` Andi Kleen
2009-12-17 14:45 ` Paul E. McKenney
2009-12-17 15:02 ` Peter Zijlstra
2009-12-17 17:53 ` Andi Kleen
2009-12-17 19:08 ` Paul E. McKenney
2009-12-17 19:55 ` Andi Kleen
2009-12-17 19:56 ` Christoph Lameter
2009-12-17 20:14 ` Peter Zijlstra
2009-12-17 20:42 ` Christoph Lameter
2009-12-18 5:17 ` Ingo Molnar
2009-12-18 17:00 ` Avi Kivity
2009-12-18 17:12 ` Ingo Molnar
2009-12-18 18:12 ` Christoph Lameter
2009-12-18 18:43 ` Andi Kleen
2009-12-18 18:45 ` Ingo Molnar
2009-12-18 23:18 ` KAMEZAWA Hiroyuki
2009-12-17 19:33 ` Christoph Lameter
2009-12-17 20:07 ` Peter Zijlstra
2009-12-17 20:13 ` Christoph Lameter
2009-12-17 20:19 ` Peter Zijlstra
2009-12-16 10:31 ` Minchan Kim
2009-12-16 10:33 ` KAMEZAWA Hiroyuki
2009-12-18 0:38 ` [RFC 0/4] speculative page fault (Was " KAMEZAWA Hiroyuki
2009-12-18 0:41 ` [RFC 1/4] uninline mm accessor KAMEZAWA Hiroyuki
2009-12-18 0:43 ` [RFC 2/4] add mm event counter KAMEZAWA Hiroyuki
2009-12-19 3:23 ` Minchan Kim
2009-12-19 6:37 ` KAMEZAWA Hiroyuki
2009-12-18 0:45 ` [RFC 3/4] lockless vma caching KAMEZAWA Hiroyuki
2009-12-19 3:43 ` Minchan Kim
2009-12-19 6:44 ` KAMEZAWA Hiroyuki
2009-12-18 0:46 ` [RFC 4/4] speculative pag fault KAMEZAWA Hiroyuki
2009-12-18 5:54 ` Minchan Kim
2009-12-18 6:06 ` KAMEZAWA Hiroyuki
2009-12-18 6:33 ` Minchan Kim
2009-12-19 3:55 ` Minchan Kim
2009-12-19 6:49 ` KAMEZAWA Hiroyuki
2009-12-16 16:24 ` [mm][RFC][PATCH 0/11] mm accessor updates Christoph Lameter
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=20091216120011.3eecfe79.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=mingo@elte.hu \
/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