qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sid Kapoor <sidkapoor2000@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] SdCard read/write performance is slow
Date: Tue, 14 Jun 2011 16:52:23 +0530	[thread overview]
Message-ID: <BANLkTikyYUfsSV0r3CwFWzmW8oUTr4vz0A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

Hi,

I am using qemu-system-arm for ARM Realview PBX-A9 board. I feel that the
performance (read/write) from the SdCard is slower than the case in which I
was mounting my rootfs through NFS. The size of my rootfs is around 3 GB. I
am making my SdCard image using qemu-img command and formatting it with ext3
filesystem. Is this a common phenomenon with everyone? Or am I doing
something wrong in the case of SdCard ?

Thanks in advance.
-- 
Siddharth Kapoor

[-- Attachment #2: Type: text/html, Size: 529 bytes --]

             reply	other threads:[~2011-06-14 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 11:22 Sid Kapoor [this message]
2011-06-14 12:23 ` [Qemu-devel] SdCard read/write performance is slow Peter Maydell

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=BANLkTikyYUfsSV0r3CwFWzmW8oUTr4vz0A@mail.gmail.com \
    --to=sidkapoor2000@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).