linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 Vs 2.4.19-rmap14a with anonymous mmaped memory
Date: Thu, 29 Aug 2002 21:34:47 +0200	[thread overview]
Message-ID: <E17kV44-00035H-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0208261525570.31523-100000@skynet>

On Monday 26 August 2002 17:13, Mel Gorman wrote:
> On Mon, 26 Aug 2002, Daniel Phillips wrote:
> 
> > Could you please provide pseudocode, to specify these reference patterns
> > more precisely?
> >
> 
> Rather than providing pseudo code, here is a link to the actual function
> that generates the smooth_sin references
> 
> http://www.csn.ul.ie/~mel/vmr/smooth_sin.html
> 
> It is really crude and written to generate any type of data until I
> found the time to generate more realistic data which is a project in
> itself. Anyone who wants to generate better data only has to edit the
> References.pm file.
> 
> It takes there inputs
> 
> references - number of references to generate
> range - the size in pages of the region to reference
> output - the output filename
> 
> the function has three parts
> 
> part 1: Plot a sin wave so that the sum of all the integer values of each
> 	part of it would generate enough references to satisify at least
> 	half of the requessted number
> part 2: Starting at the beginning of the range, reference each page in a
>         linear pattern until all the required references are generated
> part 3: Dump all references to disk
> 
> now that I think of it, it would have made more sense to begin with the
> linear reference pattern and then generate the sin curve but seeing as
> this pattern is nothing resembling real life, I didn't worry about it too
> much. It is probably something I should change as it would illustrate
> better what pages are kept in memory.

The perl script that writes tables isn't too informative without knowing
how the tables are used.  Pseudocode that says exactly what your final
reference pattern is would be a lot more useful.  Just leave out the part
about generating the tables and express it as if you were computing the
distribution at the same time as generating the references, unless it's
really impossible to do that.  I don't think it's impossible to do that
in this case.

It would also be useful to state what you define as a reference.  A user
space program read-accesses a single byte from some address?

-- 
Daniel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-08-29 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 22:22 Mel Gorman
2002-08-26 12:08 ` Daniel Phillips
2002-08-26 15:13   ` Mel Gorman
2002-08-29 19:34     ` Daniel Phillips [this message]
2002-08-29 20:53       ` Mel Gorman

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=E17kV44-00035H-00@starship \
    --to=phillips@arcor.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    /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