mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: volodya@mindspring.com
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rik van Riel <riel@conectiva.com.br>, linux-kernel@vger.kernel.org
Subject: Re: mm question
Date: Mon, 10 Dec 2001 20:52:54 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.20.0112102048390.18728-100000@node2.localnet.net> (raw)
In-Reply-To: <E16DYCI-0003Zn-00@the-village.bc.nu>



On Mon, 10 Dec 2001, Alan Cox wrote:

> > Right, but instead of trying to balance cache available memory and swap
> > my swapper will only be concerned whether the page can be evicted and
> > whether it is from the address range I want.
> 
> You want to rewrite the entire vm to have back pointers ? Right now you
> can't find pages in an address range. Its all driven from the virtual side
> without reverse lookup tables.
> 

You are right I don't want to rewrite vm. But I can go thru virtual side
taking note of the physical address. I.e. base the decision to try and
free pages not on how old the page is but on what it's physical address
is.

You see, I don't want to find a few pages in 16mb range in 512mb system.

I want to find a few pages _outside_ 64mb range in a 512mb system. 
So if I free 70mb I _will_ be able to find at least 2mb in my desired
range. In fact I won't have to free that much as they it will work is
"try to free the page", "if succeed do not return to memory pool but
instead give to the 'special region list'"

Does this make sense ?

                         Vladimir Dergachev


  reply	other threads:[~2001-12-11  1:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10 13:25 volodya
2001-12-10 13:46 ` Alan Cox
2001-12-10 13:47   ` volodya
2001-12-10 14:07     ` Alan Cox
2001-12-10 15:03       ` volodya
2001-12-10 15:21         ` Alan Cox
2001-12-10 15:40           ` Rik van Riel
2001-12-10 16:14             ` volodya
2001-12-10 16:48               ` Rik van Riel
2001-12-10 17:02                 ` volodya
2001-12-10 17:16               ` Alan Cox
2001-12-10 17:29                 ` volodya
2001-12-10 18:05                   ` Rik van Riel
2001-12-10 18:08                     ` volodya
2001-12-10 18:17                       ` Rik van Riel
2001-12-10 21:30                         ` volodya
2001-12-10 18:26                       ` Alan Cox
2001-12-10 21:27                         ` volodya
2001-12-10 21:42                           ` Alan Cox
2001-12-11  1:52                             ` volodya [this message]
2001-12-11  8:47                               ` Eric W. Biederman
2001-12-11 11:07                                 ` volodya
2001-12-11 18:39                                   ` Daniel Phillips
2001-12-10 16:05           ` volodya
2001-12-10 17:09             ` Martin J. Bligh
2001-12-10 17:16               ` Martin J. Bligh
2001-12-10 17:26               ` volodya
2001-12-10 17:25             ` Alan Cox
2001-12-10 17:38               ` volodya
2001-12-10 17:51                 ` Alan Cox
2001-12-10 17:43                   ` volodya
2001-12-10 18:12                     ` Alan Cox

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=Pine.LNX.4.20.0112102048390.18728-100000@node2.localnet.net \
    --to=volodya@mindspring.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®