All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Rodrigo S. de Castro" <rcastro@linux.ime.usp.br>
Cc: linux-mm@kvack.org
Subject: Re: ptes flags in compressed cache
Date: Thu, 26 Oct 2000 16:58:21 +0100	[thread overview]
Message-ID: <20001026165821.W20050@redhat.com> (raw)
In-Reply-To: <20001026135245.B19100@linux.ime.usp.br>; from rcastro@linux.ime.usp.br on Thu, Oct 26, 2000 at 01:52:45PM -0200

Hi,

On Thu, Oct 26, 2000 at 01:52:45PM -0200, Rodrigo S. de Castro wrote:
> 
> 	I am working on a compressed cache for 2.2.16 and I am
> currently in a cache with no compression implementation. Well, at this
> step, I gotta a doubt of how can I mark the pages (actually, ptes)
> that are in my cache and neither present in memory nor in swap. This
> is essential when I have a page fault, and this page is not present in
> memory.

Reserve a SWP_ENTRY for compressed pages.  There's precedent for that:
SHM in 2.2 already uses that mechanism for swapped-out shared memory
pages.

--Stephen
--
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.eu.org/Linux-MM/

  reply	other threads:[~2000-10-26 15:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-26 15:52 ptes flags in compressed cache Rodrigo S. de Castro
2000-10-26 15:58 ` Stephen C. Tweedie [this message]
2000-10-27  2:12   ` page fault M.Jagadish Kumar
2000-10-26 19:45     ` afei
2000-10-26 19:53       ` Rik van Riel
2000-10-27  2:14         ` afei
2000-10-27 11:17           ` Stephen C. Tweedie
     [not found]           ` <8tboe4$3bfb7$1@fido.engr.sgi.com>
2000-10-27 17:38             ` Rajagopal Ananthanarayanan
2000-10-30 12:19     ` volodya
2000-10-27  7:59   ` ptes flags in compressed cache Christoph Rohland

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=20001026165821.W20050@redhat.com \
    --to=sct@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=rcastro@linux.ime.usp.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.