From: Filip Navara <navaraf@reactos.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows.
Date: Tue, 30 Aug 2005 11:08:50 +0200 [thread overview]
Message-ID: <43142222.7000904@reactos.com> (raw)
In-Reply-To: <20050830034543.54955.qmail@web50503.mail.yahoo.com>
Francois Rioux wrote:
[snip]
> Ramdisk might have been a real performance accelerator for Windows
> hosts with enough RAM available. Since I can't find the temp memory
> image file is saved, I can't use that option.
Why do you think that it would improve performance? Sorry, but that's
complete rubbish... The guest RAM is allocated using standard virtual
memory functions and as long as you have enough memory the system will
probably leave it in the physical RAM anyway... If you don't, it's
swapped out to page file. This is much more versatile solution since you
don't have to reserve a chunk of the RAM for a disk and _permanently_
waste your memory resources this way...
>
>
> */"Jim C. Brown" <jma5@umd.edu>/* wrote:
[snip]
> IIUC this is a reference to shmfs. So this doesn't apply to KQEMU
> on Windows
> hosts. I'm not an expert on the Windows versions tho, so I'm not
> 100% sure of
> this.
>
Correct.
- Filip
next prev parent reply other threads:[~2005-08-30 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 16:56 [Qemu-devel] Re: qemu 0.7.1 + dkms-qvm86-0.7.1 (mandriva 2005 / cooker) produces version mismatch Hannes Fuchs
2005-08-29 18:05 ` [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows Francois Rioux
2005-08-29 18:53 ` John R. Hogerhuis
2005-08-29 21:59 ` Jim C. Brown
2005-08-30 7:29 ` [Qemu-devel] qemu optimization John R. Hogerhuis
2005-08-30 11:17 ` Paul Brook
2005-08-30 18:05 ` John R. Hogerhuis
2005-08-30 18:30 ` Paul Brook
2005-08-29 22:01 ` [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows Jim C. Brown
2005-08-30 3:45 ` Francois Rioux
2005-08-30 9:08 ` Filip Navara [this message]
2005-08-30 13:42 ` Francois Rioux
2005-08-30 14:02 ` Paul Brook
2005-09-03 13:51 ` ace
2005-09-03 17:35 ` Doctor Bill
2005-09-03 14:48 ` Filip Navara
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=43142222.7000904@reactos.com \
--to=navaraf@reactos.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).