public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier+lists/linux/kernel/news/@tequila.cs.yale.edu>
To: linux-kernel@vger.rutgers.edu
Subject: Re: Page coloring HOWTO [ans]
Date: 01 Feb 1999 18:11:18 -0500	[thread overview]
Message-ID: <5llnihwwh5.fsf@tequila.cs.yale.edu> (raw)
In-Reply-To: "4S1CG3.0.Tz5.-gvis"@tequila.cs.yale.edu

>>>>> "Richard" == Richard Gooch <rgooch@atnf.csiro.au> writes:
> OK, I was reading points (a) and (b) as though they were, in effect,
> the required specificiations for an algorithm to yield the best
> pages. Are they just comments on how the particular algorithm you
> mentioned works?

I believe the requirement is really something like "make the behavior more
predictable" (not just deterministic).  To reach this goal, you have to somehow
make sure that non-colliding virtual addresses turn into non-colliding physical
addresses and vice-versa (this way the compiler gets a fair chance to
statically figure out how to lay things out to avoid collisions).

Of course, the other possible requirement is just to make things more
deterministic.  It looks like Dave's alg is aiming for determinism rather than
predictability.


	Stefan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

       reply	other threads:[~1999-02-01 23:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <"4S1CG3.0.Tz5.-gvis"@tequila.cs.yale.edu>
1999-02-01 23:11 ` Stefan Monnier [this message]
1999-01-31 19:24 Page coloring HOWTO [ans] Larry McVoy
1999-01-31 22:05 ` Steve VanDevender
1999-02-01  7:20 ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
1999-01-31  8:47 Colin Plumb
1999-01-31  0:04 Larry McVoy
1999-01-31  7:25 ` David S. Miller

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=5llnihwwh5.fsf@tequila.cs.yale.edu \
    --to=monnier+lists/linux/kernel/news/@tequila.cs.yale.edu \
    --cc=linux-kernel@vger.rutgers.edu \
    /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