From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Interaction between Xen and XFS: stray RW mappings
Date: Sun, 14 Oct 2007 21:18:17 -0700
Message-ID: <4712EA09.6000102@goop.org>
References: <470FA7C3.90404@goop.org> <200710151415.07248.nickpiggin@yahoo.com.au> <4712BB05.1020701@goop.org> <200710151726.08387.nickpiggin@yahoo.com.au> <4712E1AA.501@goop.org> <20071015041133.GH995458@sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1753323AbXJOES3@vger.kernel.org>
In-Reply-To: <20071015041133.GH995458@sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
To: David Chinner <dgc@sgi.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, xfs@oss.sgi.com, Xen-devel <xen-devel@lists.xensource.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Mark Williamson <mark.williamson@cl.cam.ac.uk>, =?ISO-8859-1?Q?Morten_B=F8geskov?= <xen-users@morten.bogeskov.dk>, xfs-masters@oss.sgi.com
List-Id: xen-devel@lists.xenproject.org

David Chinner wrote:
> With defaults - little effect as vmap should never be used. It's
> only when you start using larger block sizes for metadata that this
> becomes an issue. The CONFIG_XEN workaround should be fine until we
> get a proper vmap cache....

Hm, well I saw the problem with a filesystem made with mkfs.xfs with no
options, so there must be at least *some* vmapping going on there.

    J