From: Enrico Weigelt <weigelt@nibiru.pauls.erfurt.thur.de>
To: linux-mm@kvack.org
Subject: Dynamic Swap - How to do it ?
Date: Thu, 23 Sep 1999 01:37:36 +0000 [thread overview]
Message-ID: <37E98460.9731265@nibiru.pauls.erfurt.thur.de> (raw)
hi folks,
i've trying to develop a dynamic swap manager.
i've written a little deamon which frequently reads the memory
usage from /proc and adds swapfiles if necessary. but this doesn't
really satisfy me. so i'd like to do it at kernel level,
because there could be some critical situations:
what if an application (ore more) requests very much memory very fast -
more than the swap deamon's min-space-range ? then the swap deamon
cant't increase the swapspace as fast as necessary and the application
doesn't get the memory - in the worst case the app doesnt care about it,
tries to access the (not allocated) memory and gets an SIGSEG.
so it would be better, if these applications are blocked until the swap
deamon has allocated the memory or definitively can't/won't allocate it.
but how should the kernel know which processes may be blocked and which
not. and how to reserve memory for the swap deamon ?
there should be a flag in the process status field, which tells the
kernel
that this process won't be affected by this - because it _manages_ this.
(let's say an process type MEMORY_MANAGER or something like that)
and there has to be some code in the kernel, which tells the swap deamon
when it's time to increase the swap sapce.
what do you think about this ?
how could i do this ?
bye,
ew.
-------------------------------------------
lets go to another world ... oberon
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-09-23 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-23 1:37 Enrico Weigelt [this message]
1999-09-28 3:41 ` Eric W. Biederman
1999-09-28 15:41 ` Enrico Weigelt
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=37E98460.9731265@nibiru.pauls.erfurt.thur.de \
--to=weigelt@nibiru.pauls.erfurt.thur.de \
--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