| From: |
| Andrea Arcangeli <andrea@qumranet.com> |
| To: |
| Christoph Lameter <clameter@sgi.com> |
| Subject: |
| [ofa-general] [PATCH 0 of 9] mmu notifier #v12 |
| Date: |
| Tue, 08 Apr 2008 17:44:03 +0200 |
| Message-ID: |
| <patchbomb.1207669443@duo.random> |
| Cc: |
| Nick Piggin <npiggin@suse.de>, Jack Steiner <steiner@sgi.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>, kvm-devel@lists.sourceforge.net,
Kanoj Sarcar <kanojsarcar@yahoo.com>,
Roland Dreier <rdreier@cisco.com>, linux-kernel@vger.kernel.org,
Avi Kivity <avi@qumranet.com>, linux-mm@kvack.org,
Robin Holt <holt@sgi.com>, general@lists.openfabrics.org,
Hugh Dickins <hugh@veritas.com>, akpm@linux-foundation.org |
| Archive‑link: | |
Article |
The difference with #v11 is a different implementation of mm_lock that
guarantees handling signals in O(N). It's also more lowlatency friendly.
Note that mmu_notifier_unregister may also fail with -EINTR if there are
signal pending or the system runs out of vmalloc space or physical memory,
only exit_mmap guarantees that any kernel module can be unloaded in presence
of an oom condition.
Either #v11 or the first three #v12 1,2,3 patches are suitable for inclusion
in -mm, pick what you prefer looking at the mmu_notifier_register retval and
mm_lock retval difference, I implemented and slighty tested both. GRU and KVM
only needs 1,2,3, XPMEM needs the rest of the patchset too (4, ...) but all
patches from 4 to the end can be deffered to a second merge window.
