From: Jeremy Fitzhardinge Subject: Re: Interaction between Xen and XFS: stray RW mappings Date: Sun, 21 Oct 2007 20:34:57 -0700 Message-ID: <471C1A61.1010001@goop.org> References: <470FA7C3.90404@goop.org> <20071014225618.GN23367404@sgi.com> <4712A254.4090604@goop.org> <200710151415.07248.nickpiggin@yahoo.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: dean gaudet Cc: Nick Piggin , Xen-devel , =?ISO-8859-1?Q?Morten_?=, David Chinner , Linux Kernel Mailing List , =?ISO-8859-1?Q?B=F8geskov?= , xfs@oss.sgi.com, xfs-masters@oss.sgi.com, Mark Williamson List-Id: xen-devel@lists.xenproject.org dean gaudet wrote: > On Mon, 15 Oct 2007, Nick Piggin wrote: > > >> Yes, as Dave said, vmap (more specifically: vunmap) is very expensive >> because it generally has to invalidate TLBs on all CPUs. >> > > why is that? ignoring 32-bit archs we have heaps of address space > available... couldn't the kernel just burn address space and delay global > TLB invalidate by some relatively long time (say 1 second)? > Yes, that's precisely the problem. xfs does delay the unmap, leaving stray mappings, which upsets Xen. J