From: JF Martinez <jfm2@club-internet.fr>
To: blah@kvack.org
Cc: jfm2@club-internet.fr, linux-mm@kvack.org
Subject: Re: A question about pages in stacks
Date: Thu, 13 Apr 2000 23:36:57 +0200 [thread overview]
Message-ID: <200004132136.XAA01065@agnes.bagneux.maison> (raw)
In-Reply-To: <Pine.LNX.3.96.1000413172501.13371A-100000@kanga.kvack.org> (blah@kvack.org)
>
> > Let's imagine that when looking for a pege the kerneml a page who has
> > been part of a stack frame but since then the stack has shrunk so it
> > is no longer in it. Will the kernel save it to disk or will it
> > recognize it as a page who despite what the dirty bit could say is
> > in fact free and does not need to be saved?
>
> It will have to be flushed to swap. Stack shrinkage must be explicitely
> performed, preferably using madvise. To this end, they could use a hint
> from the kernel about the actual size of the stack (see the stack
> discussions that have come up over the past week or two).
>
> -ben
>
Will I be flamed if I consider this as a weakness in Linux? While the
hardware will notify the kernel only about increasings in the stack
segment the fact is a page who is in the stack segment but on the
wrong side of the bottom of the stack is in fact a free page a nd does
not need to be written to disk. Unless that it is considered that
checking for these "false dirty" pages is so slow that it will absorb
the benefits got from the reduced number of disk writings.
--
Jean Francois Martinez
Project Independence: Linux for the Masses
http://www.independence.seul.org
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-04-13 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-13 19:58 JF Martinez
2000-04-13 21:00 ` Stephen C. Tweedie
2000-04-13 21:27 ` Benjamin C.R. LaHaise
2000-04-13 21:36 ` JF Martinez [this message]
2000-04-13 22:59 ` Benjamin C.R. LaHaise
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=200004132136.XAA01065@agnes.bagneux.maison \
--to=jfm2@club-internet.fr \
--cc=blah@kvack.org \
--cc=linux-mm@kvack.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