From: David Becker <becker@cs.duke.edu>
To: xen-devel@lists.sourceforge.net
Subject: IDE drives
Date: Wed, 24 Mar 2004 17:33:56 -0500 [thread overview]
Message-ID: <20040324223356.GA3473@cs.duke.edu> (raw)
I'm seeing quite slow IDE write performance on Xenolinux-1.2
Native linux writes at 30MB/s to an ext2 fs, and Xenolinux DOM0 gets
about 2MB/s (this is not a virtual disk extent). hdparm doesn't work
under xenolinux, but that is only part of the problem. Native linux
writes at 6MB/s without any hdparm tuning.
The SCSI hosts seem fine. native linux writes to scsi at 36MB/s and
xen at 28MB/s.
Is the IDE speed about what I should expect for xen-1.2 or did I screw
up my configuration?
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next reply other threads:[~2004-03-24 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 22:33 David Becker [this message]
2004-03-24 22:49 ` IDE drives Ian Pratt
2004-03-24 23:18 ` David Becker
-- strict thread matches above, loose matches on Subject: below --
2004-03-24 22:45 Neugebauer, Rolf
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=20040324223356.GA3473@cs.duke.edu \
--to=becker@cs.duke.edu \
--cc=xen-devel@lists.sourceforge.net \
/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.