public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: shm swapping in 2.4 again
Date: 17 Nov 2000 09:08:02 +0100	[thread overview]
Message-ID: <qwwsnorxbq5.fsf@sap.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011161929080.13085-100000@duckman.distro.conectiva>
In-Reply-To: Rik van Riel's message of "Thu, 16 Nov 2000 19:30:46 -0200 (BRDT)"

Hi Rik,

On Thu, 16 Nov 2000, Rik van Riel wrote:
> On 16 Nov 2000, Christoph Rohland wrote:
>> Also we have to make sure to derefence the swap entry if the
>> last reference is in the shm segmant table .
> 
> Why is this?

Because you never get a page fault on the shm segmants. So you never
will exchange a swap entry with a real page in these segments
automatically.

Actually I think the best approach would be to replace the entry on
the first swapin. 

Greetings
		Christoph

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

      reply	other threads:[~2000-11-17  8:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15  9:19 shm swapping in 2.4 again Christoph Rohland
2000-11-15  9:21 ` Christoph Rohland
2000-11-15 15:19 ` Rik van Riel
2000-11-15 20:52   ` Christoph Rohland
2000-11-15 21:04     ` Rik van Riel
2000-11-16  8:17       ` Christoph Rohland
2000-11-16 12:01         ` Rik van Riel
2000-11-16 19:17           ` Christoph Rohland
2000-11-16 21:31             ` Christoph Rohland
2000-11-16 21:30               ` Rik van Riel
2000-11-17  8:08                 ` Christoph Rohland [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=qwwsnorxbq5.fsf@sap.com \
    --to=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox