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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Interaction between Xen and XFS: stray RW mappings
- From: David Chinner <[email protected]>
- Re: Interaction between Xen and XFS: stray RW mappings
- References:
- Interaction between Xen and XFS: stray RW mappings
- From: Jeremy Fitzhardinge <[email protected]>
- Re: Interaction between Xen and XFS: stray RW mappings
- From: Nick Piggin <[email protected]>
- Re: Interaction between Xen and XFS: stray RW mappings
- From: Jeremy Fitzhardinge <[email protected]>
- Re: Interaction between Xen and XFS: stray RW mappings
- From: Nick Piggin <[email protected]>
- Re: Interaction between Xen and XFS: stray RW mappings
- From: Jeremy Fitzhardinge <[email protected]>
- Re: Interaction between Xen and XFS: stray RW mappings
- From: David Chinner <[email protected]>
- Interaction between Xen and XFS: stray RW mappings
- Prev by Date: Re: Interaction between Xen and XFS: stray RW mappings
- Next by Date: Re: Interaction between Xen and XFS: stray RW mappings
- Previous by thread: Re: Interaction between Xen and XFS: stray RW mappings
- Next by thread: Re: Interaction between Xen and XFS: stray RW mappings
- Index(es):
 |