linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Robert Cohen <robert@coorong.anu.edu.au>
To: Linux-MM@kvack.org
Subject: [Fwd: Can Linux learn from the Solaris VM system]
Date: Thu, 25 May 2000 20:04:07 +1000	[thread overview]
Message-ID: <392CFA97.F7F298A5@tltsu.anu.edu.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

I recently posted this to the linux -kernel list, but thought it might be
of interest here.
I dont read the MM list, so please CC any replies to me?



Robert Cohen wrote:

> Heres a short description of features added to the Solaris VM system
> recently
> http://sunsolve.Sun.COM/pub-cgi/show.pl?target=content/content8.
> I thought one of the people working on the Linux VM might be able to get
> some ideas from it.
> It talks about what Solaris does to stop cached file system data from
> treading on cached executables.
> Although it is rather short on details.
> Or do we already have systems in place to deal with this kind of
> problem?
>
> Robert Cohen

[-- Attachment #2: Type: message/rfc822, Size: 888 bytes --]

From: Robert Cohen <robert@coorong.anu.edu.au>
To: linux-kernel@vger.rutgers.edu
Subject: Can Linux learn from the Solaris VM system
Date: Wed, 17 May 2000 11:01:56 +1000
Message-ID: <3921EF84.10706F45@coorong.anu.edu.au>

Heres a short description of features added to the Solaris VM system
recently
http://sunsolve.Sun.COM/pub-cgi/show.pl?target=content/content8.
I thought one of the people working on the Linux VM might be able to get
some ideas from it.
It talks about what Solaris does to stop cached file system data from
treading on cached executables.
Although it is rather short on details.
Or do we already have systems in place to deal with this kind of
problem?

Robert Cohen



                 reply	other threads:[~2000-05-25 10:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=392CFA97.F7F298A5@tltsu.anu.edu.au \
    --to=robert@coorong.anu.edu.au \
    --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