From: Michael Brade <brade@kde.org>
To: xen-devel@lists.xensource.com
Subject: Re: PATCH: Jeremy's linux 2.6.33-pvops: wrong gntdev
Date: Wed, 4 Aug 2010 20:43:34 +0200 [thread overview]
Message-ID: <201008042043.40476.brade@kde.org> (raw)
In-Reply-To: <4C59A96D.8040506@goop.org>
[-- Attachment #1.1: Type: Text/Plain, Size: 1807 bytes --]
On Wednesday 04 August 2010 19:54:53 Jeremy Fitzhardinge wrote:
> On 08/04/2010 10:30 AM, Michael Brade wrote:
> > Ok, cool, then I'll switch back to .32. Thanks for the info! And hey, you
> > know, .35 is out already ;-) I'm really looking forward to that because
> > of the XFS improvements.
>
> Ah, you use xfs from within a domain? Does that work OK?
In Dom0, absolutely! I even have a root file system on NFS with XFS using PXE
in Dom0 and that is running without any problems so far. Just a little slow
for my taste when many small files need to be processed. Say, for instance, you
read a tar.gz file from the Dom0-NFS share, unpack it, and write the result
directly back to that NFS share. That takes a lot longer than it would take
locally, even with a Gigabit-LAN. But I hope that changes a little with 2.6.35
and the delayed logging.
The Windows-DomU (hvm-stubdom) uses a file as its harddisk on XFS and also
seems to work fine (though I am not really using it much, I have it just
because it's possible :)
The other DomUs I am currently setting up, so I can't say much about that yet.
There will be a mail server and a web server running on two of those domains,
both of them using xfs. Should there be any issues I'll let you know.
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?
cheers,
--
Michael Brade; KDE Developer
|-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
°--web: http://www.behindkde.org/people/michaelb/
KDE 4: Beyond Your Expectations
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-08-04 18:43 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 [this message]
2010-08-04 19:21 ` Jeremy Fitzhardinge
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=201008042043.40476.brade@kde.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).