From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: David Mentre <David.Mentre@irisa.fr>
Cc: Joerg Rade <jr@petz.han.de>, linux-mm <linux-mm@kvack.org>
Subject: Re: VM ideas (was: Re: TTY changes to 2.1.65)
Date: Tue, 9 Dec 1997 11:58:17 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.3.91.971209115446.690C-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <wd867ozt0eo.fsf@parafoudre.irisa.fr>
On 9 Dec 1997, David Mentre wrote:
> The interesting point of Joerg is that he see the TLB mecanism as a
> more general mecanism than just to solve swapping problems.
OK...
> As I'm a little involved in Distributed Shared Memories (with a PhD ;),
> I couldn't let such an opportunity happen without talking. I totally
> agree with Joerg. One problems with DSM is that you must track user
> memory accesses to maintain coherency. Unfortunatly, fine grain access
> like cache line is not available to the average system
> programmer. Therefore sub-page protection could be very useful.
I admit I haven't thought of that... Not having this might
be analogous to the bouncing-cache-line problem slab development
was confronted with (or just avoided?)
> Regarding DIPC, I think we could improved a little the coherency
> protocol. One big advantage of DIPC is that it provide code, and you
> can't lie with code. :) I hope I'll have more code in the future to
> explain my point of vue in DSM.
Cool, we can always use good/beautiful code...
This is especially true when I can learn new things by
reading it.
Rik.
--
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...
prev parent reply other threads:[~1997-12-09 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mng==Pine.LNX.3.91.971127141337.259F-100000@mirkwood.dummy.home>
1997-12-04 20:06 ` TTY changes to 2.1.65 Joerg Rade
1997-12-08 12:23 ` VM ideas (was: Re: TTY changes to 2.1.65) Rik van Riel
1997-12-09 7:56 ` David Mentre
1997-12-09 10:58 ` Rik van Riel [this message]
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=Pine.LNX.3.91.971209115446.690C-100000@mirkwood.dummy.home \
--to=h.h.vanriel@fys.ruu.nl \
--cc=David.Mentre@irisa.fr \
--cc=jr@petz.han.de \
--cc=linux-mm@kvack.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