public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Hans de Bruin <bruinjm@xs4all.nl>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: just a dump
Date: Thu, 28 May 2009 10:39:31 -0300	[thread overview]
Message-ID: <1243517971.2976.1059.camel@localhost.localdomain> (raw)
In-Reply-To: <4A1CEF05.6010203@xs4all.nl>

On Wed, 2009-05-27 at 09:43 +0200, Hans de Bruin wrote:
> 
> [09:09:47 INFO ] Test finished after 1 iterations.
> Memory test passed.
> [09:09:48 DEBUG] Running 'grep MemTotal /proc/meminfo'
> [09:09:48 DEBUG] Running 'rpm -qa'
> [09:09:49 INFO ]                GOOD    dma_memtest     dma_memtest 
> timestamp=1243408189    localtime=May 27 09:09:49       completed 
> successfully
> [09:09:49 DEBUG] Persistent state variable __group_level now set to 1
> [09:09:49 INFO ]        END GOOD        dma_memtest     dma_memtest 
> timestamp=1243408189    localtime=May 27 09:09:49
> [09:09:49 DEBUG] Dropping caches
> [09:09:49 DEBUG] Running 'sync'
> [09:09:51 DEBUG] Running 'sync'
> [09:09:51 DEBUG] Running 'echo 3 > /proc/sys/vm/drop_caches'
> [09:09:52 DEBUG] Persistent state variable __group_level now set to 0
> [09:09:52 INFO ] END GOOD       ----    ----    timestamp=1243408192 
> localtime=May 27 09:09:52
> 
> Well that looks good. The web page talks about forcing the system to 
> swap. That never happend swap usage is still 0 bytes. I installed 
> autotest on the same lv (3 disk stripe) as the vmdisks.

Interesting, about that I made some tests and just realized that in some
cases both mine and the original shell implementation are failing on
forcing the system to go to swap (the tests I made when the test was
firstly implemented did manage to make the machines swap, but in
conditions where the system had a significantly higher initial memory
usage). I will work on a better heuristic to force swap.

Thanks for pointing this out,

-- 
Lucas Meneghel Rodrigues
Software Engineer (QE)
Red Hat - Emerging Technologies


  reply	other threads:[~2009-05-28 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 21:12 just a dump Hans de Bruin
2009-05-12 22:20 ` Hans de Bruin
2009-05-15 14:49   ` Marcelo Tosatti
2009-05-16  8:38     ` Hans de Bruin
     [not found]       ` <20090516131046.GB3153@amt.cnet>
2009-05-21 10:22         ` Hans de Bruin
2009-05-21 10:36           ` Hans de Bruin
2009-05-21 11:03             ` Hans de Bruin
2009-05-23 21:47             ` Marcelo Tosatti
2009-05-24  8:47               ` Hans de Bruin
2009-05-24 11:49               ` Avi Kivity
2009-05-25 18:47                 ` Marcelo Tosatti
2009-05-21 13:51       ` Lucas Meneghel Rodrigues
2009-05-27  7:43         ` Hans de Bruin
2009-05-28 13:39           ` Lucas Meneghel Rodrigues [this message]
2009-07-05 18:40       ` Hans de Bruin
2009-07-06  7:39         ` Avi Kivity

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=1243517971.2976.1059.camel@localhost.localdomain \
    --to=lmr@redhat.com \
    --cc=bruinjm@xs4all.nl \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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