From: volodya@mindspring.com
To: Rik van Riel <riel@conectiva.com.br>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: mm question
Date: Mon, 10 Dec 2001 13:08:17 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.20.0112101307360.18115-100000@node2.localnet.net> (raw)
In-Reply-To: <Pine.LNX.4.33L.0112101557520.4755-100000@duckman.distro.conectiva>
On Mon, 10 Dec 2001, Rik van Riel wrote:
> On Mon, 10 Dec 2001 volodya@mindspring.com wrote:
> > On Mon, 10 Dec 2001, Alan Cox wrote:
> >
> > > > I don't want to move them - I just want to collect all that are free and
> > > > then try to free some more.
> > >
> > > How will you free them, you don't know who owns them.
> >
> > I think you misunderstood me - this allocation happens in response to
> > the system call _not_ in an interrupt handler. So it is ok to wait -
> > as long as needed. I was thinking of calling page swapper or something
> > and perhaps going after I/O buffers first.
>
> Even if you have a handle on a physical page, you don't know
> what processes are using the page, nor if there are additional
> users besides the processes.
>
> This makes it rather hard to go around trying to free pages
> within a certain physical range.
Well, what does kernel do when it runs out of memory ? For example when I
mmap a large file and start reading it back and force ?
Vladimir Dergachev
>
> cheers,
>
> Rik
> --
> DMCA, SSSCA, W3C? Who cares? http://thefreeworld.net/
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
next prev parent reply other threads:[~2001-12-10 18:10 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 [this message]
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
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.0112101307360.18115-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®