All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lukáš Doktor" <ldoktor@redhat.com>
To: KVM list <kvm@vger.kernel.org>
Subject: Re: [KVM-AUTOTEST PATCH] KVM test: Add hugepage variant
Date: Tue, 04 Aug 2009 15:00:07 +0200	[thread overview]
Message-ID: <4A7830D7.90505@redhat.com> (raw)
In-Reply-To: <20090729144104.GA21912@us.ibm.com>

Hello Ryan,

see below...

Dne 29.7.2009 16:41, Ryan Harper napsal(a):
> * Lucas Meneghel Rodrigues<lmr@redhat.com>  [2009-07-28 22:40]:
>> This patch adds a small setup script to set up huge memory
>> pages during the kvm tests execution. Also, added hugepage setup to the
>> fc8_quick sample.
>>
>> Signed-off-by: Luká?? Doktor<ldoktor@redhat.com>
>> Signed-off-by: Lucas Meneghel Rodrigues<lmr@redhat.com>
>
> Looks good.  one nit below.
>
> Signed-off-by: Ryan Harper<ryanh@us.ibm.com>
>
>> ---
>> +
>> +    def get_target_hugepages(self):
>> +        """
>> +        Calculate the target number of hugepages for testing purposes.
>> +        """
>> +        if self.vms<  self.max_vms:
>> +            self.vms = self.max_vms
>> +        vmsm = (self.vms * self.mem) + (self.vms * 64)
>
> Nit: Maybe a comment about the fudge factor being added in?

It's qemu-kvm overhead. Should I change the patch or is this explanation 
sufficient?

Thanks for the feedback,
bye, Lukáš

      reply	other threads:[~2009-08-04 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29  3:40 [KVM-AUTOTEST PATCH] KVM test: Add hugepage variant Lucas Meneghel Rodrigues
2009-07-29  3:40 ` [KVM AUTOTEST PATCH] [RFC] KVM test: keep record of supported qemu options Lucas Meneghel Rodrigues
2009-07-29  8:11   ` Lukáš Doktor
2009-07-29 12:11     ` [Autotest] " Lucas Meneghel Rodrigues
2009-07-29  8:02 ` [KVM-AUTOTEST PATCH] KVM test: Add hugepage variant Lukáš Doktor
2009-07-29 14:41 ` Ryan Harper
2009-08-04 13:00   ` Lukáš Doktor [this message]

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=4A7830D7.90505@redhat.com \
    --to=ldoktor@redhat.com \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.