kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Doktor <ldoktor@redhat.com>
To: ldoktor@redhat.com
Cc: jzupka@redhat.com, kvm@vger.kernel.org, autotest@test.kernel.org,
	jasowang@redhat.com, lmr@redhat.com
Subject: [KVM_AUTOTEST][PATCH] KSM_overcommit: dynamic reserve calculation (2)
Date: Sat,  8 May 2010 18:01:07 +0100	[thread overview]
Message-ID: <1273338071-8595-1-git-send-email-ldoktor@redhat.com> (raw)
In-Reply-To: <[KVM_AUTOTEST][PATCH] KSM_overcommit: dynamic reserve calculation (2)>

Hi,

thanks for nice page about git workflow. I always wanted to try it but never had the time to sit down and learn...

Booth the TMPFS and 0.055 guest_reserve constant are set empirically using various RHEL and Fedora guest/hosts. Smaller hosts can work with smaller (0.045) constant but we didn't want to make the code more complex to exactly fit the limits.

Original changelog:
* NEW: guest_reserve and host_reserve are now calculated based on used memory
* NEW: tmpfs reserve is also evaluated to fit the overhead
* NEW: VM alive check during split_guest()
* FIX: In function split_guest() we used incorrect session
* MOD: Increase number of VNC ports

Best regards,
Lukas



       reply	other threads:[~2010-05-08 17:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[KVM_AUTOTEST][PATCH] KSM_overcommit: dynamic reserve calculation (2)>
2010-05-08 17:01 ` Lukas Doktor [this message]
2010-05-12 21:59   ` [Autotest] [KVM_AUTOTEST][PATCH] KSM_overcommit: dynamic reserve calculation (2) Lucas Meneghel Rodrigues
2010-05-08 17:01 ` [PATCH 1/4] Increase maximum number of VNC ports Lukas Doktor
2010-05-17 20:34   ` Lucas Meneghel Rodrigues
2010-05-08 17:01 ` [PATCH 2/4] Add VMs alive check while spliting the guest's pages Lukas Doktor
2010-05-08 17:01 ` [PATCH 3/4] FIX: Incorrect session in function split_guest() Lukas Doktor
2010-05-08 17:01 ` [PATCH 4/4] guest_reserve, host_reserve and tmpfs overhead automatic calculation based on used memory Lukas Doktor

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=1273338071-8595-1-git-send-email-ldoktor@redhat.com \
    --to=ldoktor@redhat.com \
    --cc=autotest@test.kernel.org \
    --cc=jasowang@redhat.com \
    --cc=jzupka@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@redhat.com \
    /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).