[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A7031D.5080300@gmail.com>
Date: Wed, 25 Jul 2007 10:00:29 +0200
From: Rene Herman <rene.herman@...il.com>
To: david@...g.hm
CC: Ray Lee <ray-lk@...rabbit.org>,
Nick Piggin <nickpiggin@...oo.com.au>,
Jesper Juhl <jesper.juhl@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
ck list <ck@....kolivas.org>, Ingo Molnar <mingo@...e.hu>,
Paul Jackson <pj@....com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.23
On 07/25/2007 06:46 AM, david@...g.hm wrote:
> you could make a synthetic test by writing a memory hog that allocates
> 3/4 of your ram then pauses waiting for input and then randomly accesses
> the memory for a while (say randomly accessing 2x # of pages allocated)
> and then pausing again before repeating
Something like this?
> run two of these, alternating which one is running at any one time. time
> how long it takes to do the random accesses.
>
> the difference in this time should be a fair example of how much it
> would impact the user.
Notenotenote, not sure what you're going to show with it (times are simply
as horrendous as I'd expect) but thought I'd try to inject something other
than steaming cups of 4-letter beverages.
Rene.
View attachment "hog.c" of type "text/plain" (975 bytes)
Powered by blists - more mailing lists