[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080122203125.GC15848@v2.random>
Date: Tue, 22 Jan 2008 21:31:25 +0100
From: Andrea Arcangeli <andrea@...ranet.com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Izik Eidus <izike@...ranet.com>, Rik van Riel <riel@...hat.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
kvm-devel@...ts.sourceforge.net, Avi Kivity <avi@...ranet.com>,
clameter@....com, daniel.blueman@...drics.com, holt@....com,
steiner@....com, Andrew Morton <akpm@...l.org>,
Hugh Dickins <hugh@...itas.com>, Nick Piggin <npiggin@...e.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [PATCH] mmu notifiers #v3
On Tue, Jan 22, 2008 at 08:28:47PM +0100, Peter Zijlstra wrote:
> I think we can get rid of this rwlock as I think this will seriously
> hurt larger machines.
Yep, I initially considered it, nevertheless given you solved part of
the complication I can add it now ;). The only technical reason for
not using RCU is if certain users of the notifiers are registering and
unregistering at high frequency through objects that may need to be
freed quickly.
I can tell the KVM usage of the mmu notifiers is sure fine to use RCU.
Then I will have to update KVM so that it will free the kvm structure
after waiting a quiescent point to avoid kernel crashing memory
corruption after applying your changes to the mmu notifier.
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists