| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings |
| From: | Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
| Date: | Sun, 14 Oct 2007 21:18:17 -0700 |
| Cc: | Nick Piggin <nickpiggin@xxxxxxxxxxxx>, xfs@xxxxxxxxxxx, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, Morten Bøgeskov <xen-users@xxxxxxxxxxxxxxxxxx>, xfs-masters@xxxxxxxxxxx |
| In-reply-to: | <20071015041133.GH995458@sgi.com> |
| 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> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.5 (X11/20070727) |
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
|
| Previous by Date: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, David Chinner |
|---|---|
| Next by Date: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, David Chinner |
| Previous by Thread: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, David Chinner |
| Next by Thread: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |