| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings
|
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Subject: |
[Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings |
|
From: |
David Chinner <dgc@xxxxxxx> |
|
Date: |
Mon, 15 Oct 2007 14:25:46 +1000 |
|
Cc: |
Nick Piggin <nickpiggin@xxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, David Chinner <dgc@xxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Morten Bøgeskov <xen-users@xxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, Mark Williamson <mark.williamson@xxxxxxxxxxxx> |
|
Delivery-date: |
Mon, 15 Oct 2007 04:01:03 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<4712EA09.6000102@xxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<470FA7C3.90404@xxxxxxxx> <200710151415.07248.nickpiggin@xxxxxxxxxxxx> <4712BB05.1020701@xxxxxxxx> <200710151726.08387.nickpiggin@xxxxxxxxxxxx> <4712E1AA.501@xxxxxxxx> <20071015041133.GH995458@xxxxxxx> <4712EA09.6000102@xxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.4.2.1i |
On Sun, Oct 14, 2007 at 09:18:17PM -0700, Jeremy Fitzhardinge wrote:
> 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.
Sorry - I should have been more precise - vmap should never be used in
performance critical paths on default configs. Log recovery will
trigger vmap/vunmap usage, so this is probably what you are seeing.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Interaction between Xen and XFS: stray RW mappings, Jeremy Fitzhardinge
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, dean gaudet
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Jeremy Fitzhardinge
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, dean gaudet
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Nick Piggin
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Jeremy Fitzhardinge
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Jeremy Fitzhardinge
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Andi Kleen
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Jeremy Fitzhardinge
- [Xen-devel] Re: Interaction between Xen and XFS: stray RW mappings, Andi Kleen
|
|
|
| |
|
Home