qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org, Ottavio Caruso <pr0f3ss0r1492@yahoo.com>
Subject: Re: [Qemu-devel] -snapshot and tmpsfs
Date: Sun, 19 Nov 2006 16:57:25 +0700	[thread overview]
Message-ID: <200611191657.25848.a_mulyadi@softhome.net> (raw)
In-Reply-To: <964923.2721.qm@web52601.mail.yahoo.com>

Hi Ottavio 
> Are the writes to tmpfs (in a *nix guest OS) recorded to the
> snapshotted image?
>
> Example: /var/run on tmpfs
> OS writes to /var/run. Bigger temp file or not?

>From what I saw, the temp file isn't bigger unless the tmpfs' size is 
exceeding the simulated RAM size, thus some of them are getting into 
the simulated swap...in this case, the snapshot image. 

Qemu itself already allocates a memory area as big as the argument you 
gave in -m. Here is something you see if you use -m 64 like I did:
42131000 (69968 KB)    rw-p (00:00 0)

(Because of the work of demand paging, this VMA size doesn't 
neccessarily reflect the size of the actual allocated pages).


I also try to diff the lsof's output and pmap's output before and after 
I write 43 MB of zero-filled file in tmpfs-based directory (while the 
size of tmpfs itself is 44MB) and I only get these:
# diff -u pmap{1,3}.txt
--- pmap1.txt   2006-11-19 16:31:44.000000000 +0700
+++ pmap3.txt   2006-11-19 16:33:54.000000000 +0700
@@ -1,7 +1,7 @@
 qemu(5017)
 08048000 (688 KB)      r-xp (16:02 897438)   
/usr/local/qemu080/bin/qemu
 080f4000 (36 KB)       rw-p (16:02 897438)   
/usr/local/qemu080/bin/qemu
-080fd000 (27372 KB)    rwxp (00:00 0)
+080fd000 (27384 KB)    rwxp (00:00 0)
 40000000 (84 KB)       r-xp (16:02 244393)   /lib/ld-2.3.2.so
 40015000 (4 KB)        rw-p (16:02 244393)   /lib/ld-2.3.2.so
 40016000 (4 KB)        rw-p (00:00 0)
@@ -36,4 +36,4 @@
 4212e000 (12 KB)       rw-p (16:02 651591)   /lib/tls/libc-2.3.2.so
 42131000 (69968 KB)    rw-p (00:00 0)
 bfff4000 (48 KB)       rwxp (00:00 0)
-mapped:   102288 KB writable/private: 98144 KB shared: 564 KB
+mapped:   102300 KB writable/private: 98156 KB shared: 564 KB

My conclusion: temp file will get bigger if we write something bigger 
than simulated RAM size (but still smaller than tmpfs size, of 
course..).

regards,

Mulyadi

  parent reply	other threads:[~2006-11-20  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-18 14:35 [Qemu-devel] -snapshot and tmpsfs Ottavio Caruso
2006-11-18 15:39 ` Michael McConnell
2006-11-19  9:57 ` Mulyadi Santosa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-19 12:25 Ottavio Caruso

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=200611191657.25848.a_mulyadi@softhome.net \
    --to=a_mulyadi@softhome.net \
    --cc=pr0f3ss0r1492@yahoo.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).