From: "Antonino Ingargiola" <tritemio@gmail.com>
To: "Con Kolivas" <kernel@kolivas.org>
Cc: "ck list" <ck@vds.kolivas.org>,
"linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.22-rc3-ck1
Date: Tue, 29 May 2007 21:59:34 +0200 [thread overview]
Message-ID: <5486cca80705291259s63edf2bcv7035f700aa23e8b1@mail.gmail.com> (raw)
In-Reply-To: <5486cca80705291253vb793caqd632f3adbb2479ad@mail.gmail.com>
2007/5/29, Antonino Ingargiola <tritemio@gmail.com>:
[cut]
> Swap Prefetch OFF
> # ./sp_tester
> Ram 776388000 Swap 514040000
> Total ram to be malloced: 1033408000 bytes
> Starting first malloc of 516704000 bytes
> Starting 1st read of first malloc
> Touching this much ram takes 1642 milliseconds
> Starting second malloc of 516704000 bytes
> Completed second malloc and free
> Sleeping for 60 seconds
> Important part - starting reread of first malloc
> Completed read of first malloc
> Timed portion 9089 milliseconds
>
>
> Swap Prefetch OFF
> # ./sp_tester
> Ram 776388000 Swap 514040000
> Total ram to be malloced: 1033408000 bytes
> Starting first malloc of 516704000 bytes
> Starting 1st read of first malloc
> Touching this much ram takes 1635 milliseconds
> Starting second malloc of 516704000 bytes
> Completed second malloc and free
> Sleeping for 60 seconds
> Important part - starting reread of first malloc
> Completed read of first malloc
> Timed portion 1783 milliseconds
The second case is clearly with swap prefetch *ON*, sorry.
~ Antonio
next prev parent reply other threads:[~2007-05-29 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705270800.06612.kernel@kolivas.org>
2007-05-29 19:53 ` Antonino Ingargiola
2007-05-29 19:59 ` Antonino Ingargiola [this message]
2007-05-31 2:03 ` Re:swap prefetch improvements Con Kolivas
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=5486cca80705291259s63edf2bcv7035f700aa23e8b1@mail.gmail.com \
--to=tritemio@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=kernel@kolivas.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®