public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: Google's mm problem - not reproduced on 2.4.13
Date: Sat, 3 Nov 2001 00:16:46 +0000 (UTC)	[thread overview]
Message-ID: <9rvd1e$vk$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111021250560.20078-100000@penguin.transmeta.com> <Pine.LNX.4.33.0111021303060.20128-100000@penguin.transmeta.com> <20011102222754.2366f1f5.skraw@ithnet.com>

In article <20011102222754.2366f1f5.skraw@ithnet.com>,
Stephan von Krawczynski  <skraw@ithnet.com> wrote:
>
>> -	/* Don't swap out areas which are locked down */
>> -	if (vma->vm_flags & (VM_LOCKED|VM_RESERVED))
>> +	/* Don't swap out areas which are reserved */
>> +	if (vma->vm_flags & VM_RESERVED)
>>  		return count;
>
>Although I agree what you said about differences of old and new VM, I believe
>the above was not really what Ben intended to do by mlocking. I mean, you swap
>them out right now, or not?

Not. See where I added the VM_LOCKED test - deep down in the page-out
code it will decide that a VM_LOCKED page is always accessed, and will
move it to the active list instead of swapping it out.

		Linus

  reply	other threads:[~2001-11-03  0:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0111021250560.20078-100000@penguin.transmeta.com>
2001-11-02 21:13 ` Google's mm problem - not reproduced on 2.4.13 Linus Torvalds
2001-11-02 21:27   ` Stephan von Krawczynski
2001-11-03  0:16     ` Linus Torvalds [this message]
2001-10-31 18:06 Daniel Phillips
2001-10-31 20:39 ` Daniel Phillips
2001-10-31 20:45   ` Andrea Arcangeli
2001-10-31 21:03     ` Daniel Phillips
2001-10-31 21:53       ` Andreas Dilger
2001-11-01  4:52         ` Daniel Phillips
2001-10-31 22:12       ` Ben Smith
2001-11-01  0:34         ` Andrea Arcangeli
2001-11-02 17:51         ` Sven Heinicke
2001-11-02 18:00           ` Andrea Arcangeli
2001-11-02 18:19             ` Daniel Phillips
2001-11-02 20:27               ` Linus Torvalds
2001-11-02 21:08                 ` Ben Smith
2001-11-02 21:20                   ` Linus Torvalds
2001-11-02 22:42                     ` Ben Smith
2001-11-02 23:15                       ` Daniel Phillips
2001-11-02 21:12                 ` Rik van Riel
     [not found]               ` <200111022027.fA2KRwe20006@penguin.transmeta.com>
2001-11-02 20:58                 ` Daniel Phillips
2001-11-02 18:11           ` Daniel Phillips
2001-11-02 18:48             ` Sven Heinicke
2001-11-02 18:57               ` Daniel Phillips
2001-11-01  0:19     ` Daniel Phillips
2001-11-01  0:29       ` Andrea Arcangeli
2001-11-01  1:17       ` Ben Smith
2001-11-01  1:41         ` Rik van Riel
2001-11-01  1:55           ` Ben Smith
2001-11-01  2:06             ` Andrea Arcangeli
2001-10-31 20:48   ` Rik van Riel
2001-10-31 21:04     ` Daniel Phillips
2001-10-31 21:08       ` Rik van Riel

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='9rvd1e$vk$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.com \
    --cc=linux-kernel@vger.kernel.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