|| ||Peter Zijlstra <email@example.com> |
|| ||Andrea Arcangeli <firstname.lastname@example.org>,
Avi Kivity <email@example.com>,
Thomas Gleixner <firstname.lastname@example.org>,
Rik van Riel <email@example.com>, Ingo Molnar <firstname.lastname@example.org>,
Linus Torvalds <email@example.com> |
|| ||[PATCH 00/20] mm: Preemptibility -v5 |
|| ||Mon, 18 Oct 2010 13:24:33 +0200|
|| ||firstname.lastname@example.org, email@example.com,
Benjamin Herrenschmidt <firstname.lastname@example.org>,
David Miller <email@example.com>,
Hugh Dickins <firstname.lastname@example.org>,
Mel Gorman <email@example.com>, Nick Piggin <firstname.lastname@example.org>,
Peter Zijlstra <email@example.com>,
Paul McKenney <firstname.lastname@example.org>,
Yanmin Zhang <email@example.com>,
Stephen Rothwell <firstname.lastname@example.org>|
|| ||Article, Thread
This patch-set makes part of the mm a lot more preemptible. It converts
i_mmap_lock and anon_vma->lock to mutexes and makes mmu_gather fully
The main motivation was making mm_take_all_locks() preemptible, since it
appears people are nesting hundreds of spinlocks there.
The side-effects are that can finally make mmu_gather preemptible,
something which lots of people have wanted to do for a long time.
It also gets us anon_vma refcounting, which seems to result in a nice
cleanup of the anon_vma lifetime rules wrt KSM and compaction.
This patch-set it build and boot-tested on x86_64 (a previous version was
also tested on Dave's Niagra2 machines, and I suppose s390 was too when
Martin provided the conversion patch for his arch).
There are no known architectures left unconverted.
Yanmin ran the -v3 posting through the comprehensive Intel test farm
and didn't find any regressions.
( Not included in this posting are the 4 Sparc64 patches that implement
gup_fast, those can be applied separately after this series gets
The full series (including the Sparc64 gup_fast bits) also available in -git
form from (against Linus' tree as of about an hour ago):
DaveM mentioned some sparc64 trouble with the -v4 posting, this turned out to
be a false positive as unpatched kernels also are having trouble on his
Linus, Andrew, Stephen, can we add this to -next for .37?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/