From: Jan Astalos <astalos@tuke.sk>
To: Andrey Savochkin <saw@saw.sw.com.sg>
Cc: linux-mm@kvack.org, Yuri Pudgorodsky <yur@asplinux.ru>
Subject: Re: Question: memory management and QoS
Date: Mon, 28 Aug 2000 11:28:15 +0200 [thread overview]
Message-ID: <39AA30AF.14C17C50@tuke.sk> (raw)
In-Reply-To: <20000828154744.A3741@saw.sw.com.sg>
Andrey Savochkin wrote:
>
> Hello,
Hi.
>
> I don't think that personal swapfiles is an efficient approach to achieve
> QoS. Most of the space will be reserved for exceptional cases, and, thus,
> wasted, as Yuri has mentioned. A shared swap space allowing exceeding the
> guaranteed amount (if the memory isn't really used) is much more efficient
> spending of the space. If the system has some spare memory, users exceeding
> their limits may still use it (but, certainly, only if only some of them, not
> all, exceed the limits). Moreover, if some users don't consume all the
> memory guaranteed to them, others may temporarily use it.
I think I explained my points clearly enough in my second reply to Yuri so I won't
repeat it again.
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.
Please, don't repeat Yuri's argument with unswapable kernel objects and locked
memory. Users should be able to lock only memory inside their own allocation
and kernel objects should be accounted to this kind of memory too. Whether
it is easy or hard to implement really does not matter for design. Anyway, there
still could be pool of memory allocated to anonymous objects...
I think that your beancounter is a big step towards good QoS in Linux MM, but
I'm a bit confused when I'll hear "...users exceeding their limits". What's the
limit good for if it can be exceeded ? Can you rethought the term ?
Can you describe how to avoid VM shortage by beancounter ?
Other than I described in my first reply to Yuri (point A) .
Regards,
Jan
--
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 9:28 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 [this message]
2000-08-28 11:30 ` Andrey Savochkin
2000-08-28 12:38 ` Jan Astalos
2000-08-28 17:25 ` Rik van Riel
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=39AA30AF.14C17C50@tuke.sk \
--to=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