From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael Brade <brade@kde.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: PATCH: Jeremy's linux 2.6.33-pvops: wrong gntdev
Date: Wed, 04 Aug 2010 12:21:55 -0700 [thread overview]
Message-ID: <4C59BDD3.6060602@goop.org> (raw)
In-Reply-To: <201008042043.40476.brade@kde.org>
On 08/04/2010 11:43 AM, Michael Brade wrote:
> XFS has been my filesystem of choice for at least 5 years I think. Never had
> any issues with it. Before I used reiserfs and before that I had ext2/3 but
> that one gave me too many problems so I never tried it again.
>
> Would you recommend anything else instead?
I ask because xfs does some memory mapping tricks which are actually
fairly awkward to handle in a PV Xen domain. We end up disabling its
lazy vunmap behaviour, which means there's a bit more overhead from tlb
flushes and the like. I don't know what kind of performance effect that
actually has, or in what circumstances.
J
prev parent reply other threads:[~2010-08-04 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 19:27 PATCH: Jeremy's linux 2.6.33-pvops: wrong gntdev Michael Brade
2010-08-02 13:41 ` Pasi Kärkkäinen
2010-08-02 15:26 ` Jeremy Fitzhardinge
2010-08-04 17:30 ` Michael Brade
2010-08-04 17:54 ` Jeremy Fitzhardinge
2010-08-04 18:43 ` Michael Brade
2010-08-04 19:21 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C59BDD3.6060602@goop.org \
--to=jeremy@goop.org \
--cc=brade@kde.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.