All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: "Stephen C. Tweedie" <sct@redhat.com>,
	Christoph Rohland <cr@sap.com>,
	linux-kernel@vger.kernel.org
Subject: Re: VM subsystem bug in 2.4.0 ?
Date: Tue, 09 Jan 2001 17:45:19 +0100	[thread overview]
Message-ID: <3A5B401F.9D4BCBDF@innominate.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10101081003410.3750-100000@penguin.transmeta.com> <Pine.LNX.4.21.0101081621590.21675-100000@duckman.distro.conectiva> <20010109140932.E4284@redhat.com> <qwwhf387p4s.fsf@sap.com> <20010109153119.G9321@redhat.com> <qwwd7dw7mrd.fsf@sap.com> <20010109160511.I9321@redhat.com>

"Stephen C. Tweedie" wrote:
> On Tue, Jan 09, 2001 at 04:45:10PM +0100, Christoph Rohland wrote:
> >
> > AFAIU mlock'ed pages would never get deactivated since the ptes do not
> > get dropped.
> 
> D'oh, right --- so can't you lock a segment just by bumping page_count
> on its pages?

Putting this together with an idea from Linus:

Linus Torvalds wrote:
> On Mon, 8 Jan 2001, Rik van Riel wrote:
> >
> > We need a check in deactivate_page() to prevent the kernel
> > from moving pages from locked shared memory segments to the
> > inactive_dirty list.
> >
> > Christoph?  Linus?
> 
> The only solution I see is something like a "active_immobile" list, and
> add entries to that list whenever "writepage()" returns 1 - instead of
> just moving them to the active list.

Call it 'pinned'... the pinned list would have pages with use count = 2
or more.  A page gets off the pinned list when its use count goes to 1
in put_page.

--
Daniel
-
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/

  parent reply	other threads:[~2001-01-09 16:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08  8:46 VM subsystem bug in 2.4.0 ? Sergey E. Volkov
2001-01-08 18:00 ` Rik van Riel
2001-01-08 18:10   ` Linus Torvalds
2001-01-08 18:30     ` Rik van Riel
2001-01-09  7:52       ` Christoph Rohland
2001-01-09 14:09       ` Stephen C. Tweedie
2001-01-09 14:53         ` Christoph Rohland
2001-01-09 15:31           ` Stephen C. Tweedie
2001-01-09 15:45             ` Christoph Rohland
2001-01-09 16:05               ` Stephen C. Tweedie
2001-01-09 16:17                 ` Christoph Rohland
2001-01-09 18:37                   ` Linus Torvalds
2001-01-09 16:45                 ` Daniel Phillips [this message]
2001-01-17  8:33                   ` Rik van Riel
2001-01-18  8:23                     ` Christoph Rohland
2001-01-25 22:47                       ` Daniel Phillips
2001-01-09 18:36             ` Linus Torvalds
2001-01-09 18:23         ` Linus Torvalds
2001-01-09 22:20           ` Christoph Rohland
2001-01-09 22:59             ` Linus Torvalds
2001-01-10  7:33               ` Christoph Rohland
2001-01-10 15:50               ` Tim Wright

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=3A5B401F.9D4BCBDF@innominate.de \
    --to=phillips@innominate.de \
    --cc=cr@sap.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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.