From: Rik van Riel <riel@conectiva.com.br>
To: Jan Astalos <astalos@tuke.sk>
Cc: Andrey Savochkin <saw@saw.sw.com.sg>,
linux-mm@kvack.org, Yuri Pudgorodsky <yur@asplinux.ru>
Subject: Re: Question: memory management and QoS
Date: Mon, 28 Aug 2000 14:25:10 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0008281421180.18553-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <39AA30AF.14C17C50@tuke.sk>
On Mon, 28 Aug 2000, Jan Astalos wrote:
> I still claim that per user swapfiles will:
> - be _much_ more efficient in the sense of wasting disk space (saving money)
> because it will teach users efficiently use their memory resources (if
> user will waste the space inside it's own disk quota it will be his own
> problem)
> - provide QoS on VM memory allocation to users (will guarantee amount of
> available VM for user)
> - be able to improve _per_user_ performance of system (localizing performance
> problems to users that caused them and reducing disk seek times)
> - shift the problem with OOM from system to user.
Do you have any reasons for this, or are you just asserting
them as if they were fact? ;)
I think we can achieve the same thing, with higher over-all
system performance, if we simply give each user a VM quota
and do the bookkeeping on a central swap area.
The reasons for this are multiple:
1) having one swap partition will reduce disk seeks
(no matter how you put it, disk seeks are a _system_
thing, not a per user thing)
2) not all users are logged in at the same time, so you
can do a minimal form of overcomitting here (if you want)
3) you can easily give users _2_ VM quotas, a guaranteed one
and a maximum one ... if a user goes over the guaranteed
quota, processes can be killed in OOM situations
(this allows each user to make their own choices wrt.
overcommitment)
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
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-08-28 17:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-24 10:13 Jan Astalos
2000-08-28 7:47 ` Andrey Savochkin
2000-08-28 9:28 ` Jan Astalos
2000-08-28 11:30 ` Andrey Savochkin
2000-08-28 12:38 ` Jan Astalos
2000-08-28 17:25 ` Rik van Riel [this message]
2000-08-30 7:38 ` Jan Astalos
2000-08-30 16:53 ` Rik van Riel
2000-08-31 1:48 ` Andrey Savochkin
2000-08-31 11:49 ` Jan Astalos
2000-08-25 13:22 Yuri Pudgorodsky
2000-08-25 15:51 ` Jan Astalos
2000-08-25 20:17 ` Yuri Pudgorodsky
2000-08-28 8:36 ` Jan Astalos
2000-08-28 11:05 ` Andrey Savochkin
2000-08-28 12:10 ` Jan Astalos
2000-08-28 13:10 ` Andrey Savochkin
2000-08-30 9:01 ` Jan Astalos
2000-08-30 11:42 ` Marco Colombo
2000-08-28 17:40 ` Rik van Riel
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.21.0008281421180.18553-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=astalos@tuke.sk \
--cc=linux-mm@kvack.org \
--cc=saw@saw.sw.com.sg \
--cc=yur@asplinux.ru \
/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