From: Andrea Arcangeli <aarcange@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Sagi Grimberg <sagig@mellanox.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Haggai Eran <haggaie@mellanox.com>
Subject: [PATCH] mmu notifier srcu
Date: Thu, 23 Aug 2012 20:01:14 +0200 [thread overview]
Message-ID: <1345744875-26224-1-git-send-email-aarcange@redhat.com> (raw)
Hi Andrew,
Now that the i_mmap_mutex and anon_vma.lock are mutexes, it's easier
to allow all mmu notifier methods to schedule. This is the first patch
that is required to allow that. Others will follow shortly.
This has been updated compared to previous versions, according to
Peter's suggestion to make the srcu global to save per-cpu memory
(originally there was a srcu object in every mmu notifier
structure). This slightly increases contention in the
mmu_notifier_unregister or exit_mmap paths. But that's by far not a
concern for KVM and hopefully for all other mmu notifier users.
Sagi Grimberg (1):
mm: mmu_notifier: have mmu_notifiers use a global SRCU so they may
safely schedule
include/linux/mmu_notifier.h | 1 +
mm/mmu_notifier.c | 73 +++++++++++++++++++++++++++--------------
2 files changed, 49 insertions(+), 25 deletions(-)
--
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:[~2012-08-23 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 18:01 Andrea Arcangeli [this message]
2012-08-23 18:01 ` [PATCH] mm: mmu_notifier: have mmu_notifiers use a global SRCU so they may safely schedule Andrea Arcangeli
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=1345744875-26224-1-git-send-email-aarcange@redhat.com \
--to=aarcange@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=haggaie@mellanox.com \
--cc=linux-mm@kvack.org \
--cc=sagig@mellanox.com \
--cc=xiaoguangrong@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).