qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Krysik <piotrek_priv@yahoo.com>
To: Kuniyasu Suzaki <k.suzaki@aist.go.jp>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU with KNOPPIX
Date: Thu, 26 Aug 2004 05:56:34 -0700 (PDT)	[thread overview]
Message-ID: <20040826125634.18345.qmail@web52507.mail.yahoo.com> (raw)
In-Reply-To: <1093500780.21464.780.camel@aragorn>

Hi,

Probably a lot of CPU is spend on decompressing 
in CLOOP driver. Maybe it could be possible to 
do decompression natively and not under emulated 
CPU.

You can start with an exercise. Setup CLOOP on 
your host (e.g. run Knoppix natively), then run 
another Knoppix inside Qemu, but give it access 
to your CLOOP device as an ide drive:
  qemu ... -cdrom /dev/cdrom -hda /dev/<your cloop>
Now try to use your host cloop device inside Qemu. 
E.g. mount it instead of guest cloop:
  mount ... /dev/hda <guest cloop mount point>
Play with it. If the performance difference 
is substantial, it may justify extra effort 
to implement cloop compatible Qemu disk format 
(I guess qcow is not compatible with cloop), 
so it can be used on Windows.

I didn't try this, so cannot guarantee that it 
will work. Contact me if you would like to try 
this and need assistance.


Regards,

Piotrek

--- "John R. Hogerhuis" <jhoger@pobox.com> wrote:

> On Wed, 2004-08-25 at 22:19, Kuniyasu Suzaki wrote:
> 
> > If you have any suggestions, please post.
> 
> Need to think of some ways to speed it up. It took
> several minutes to
> load.
> 
> Where are the possible optimizations?
> 
> Could we do a "save state" type operation and jump
> straight to loaded
> Knoppix desktop?
> 
> Seems to be a lot of CDROM activity. That is the
> nature of Knoppix, and
> that definitely slows Knoppix down, but for some
> reason it sounded
> really choppy to me. I'm wondering if there is
> anything we can do to
> speed up cd access. Maybe on a machine with a lot of
> RAM it could be
> read into RAM, or perhaps just copied to hard drive
> in one step and run
> from there. Some or all apps could be decompressed.
> I think Knoppix has
> something like this.
> 
> It's a complex set up, but some profiling might be
> in order... see how
> well QEMU translation cache is performing, and see
> if there is a lot of
> time spent in certain types of code that could be
> sped up in QEMU.
> 
> 
> I agree with you that Kazu's recent QEMU on Windows
> was indeed the heavy
> lifting, but there's still plenty to do on (Knoppix
> On (QEMU On
> Windows)) to make it really usable. Which I think it
> can be, and on some
> machines maybe it already is...
> 
> -- John.
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 




		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

  parent reply	other threads:[~2004-08-26 14:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  7:09 [Qemu-devel] QEMU with KNOPPIX Kuniyasu Suzaki
2004-08-25 10:02 ` John R. Hogerhuis
2004-08-26  5:19   ` Kuniyasu Suzaki
2004-08-26  6:13     ` John R. Hogerhuis
2004-08-26  7:57       ` Kuniyasu Suzaki
2004-08-26  9:34         ` John R. Hogerhuis
2004-08-27  5:58           ` Kuniyasu Suzaki
2004-08-26 11:41         ` Johannes Schindelin
2004-08-26 12:56       ` Piotr Krysik [this message]
2004-08-26 15:49         ` Johannes Schindelin
2004-08-27  6:06         ` Kuniyasu Suzaki
2004-08-27  8:35           ` Piotr Krysik
2004-08-27 10:08             ` Johannes Schindelin
2004-08-27 17:00               ` Cloop-Driver, was " Johannes Schindelin
2004-08-27 20:40                 ` Juergen Lock
2004-08-29 13:52                   ` Johannes Schindelin
2004-08-30  4:32                     ` coLinux and " Kuniyasu Suzaki
2004-08-27 22:32                 ` Fabrice Bellard
2004-08-27 22:40       ` Fabrice Bellard
2004-08-28  3:53         ` Kuniyasu Suzaki

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=20040826125634.18345.qmail@web52507.mail.yahoo.com \
    --to=piotrek_priv@yahoo.com \
    --cc=k.suzaki@aist.go.jp \
    --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).