[mm][RFC][PATCH 0/11] mm accessor updates.

KAMEZAWA Hiroyuki
2009-12-16T03:03:25Z

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