From: "Al Boldi" <a1426z@gawab.com>
To: "'Nix'" <nix@esperi.org.uk>
Cc: "'Marcelo Tosatti'" <marcelo.tosatti@cyclades.com>,
<linux-kernel@vger.kernel.org>
Subject: RE: Kswapd flaw
Date: Tue, 28 Jun 2005 16:52:00 +0300 [thread overview]
Message-ID: <200506281352.QAA25851@raad.intranet> (raw)
In-Reply-To: <87irzy63xx.fsf@amaterasu.srvr.nix>
Hi Nix, how are you?
You wrote: {
On 28 Jun 2005, Al Boldi yowled:
> Nix wrote:
>> On 28 Jun 2005, Al Boldi murmured woefully:
>>> Kswapd starts evicting processes to fullfil a malloc, when it should
>>> just deny it because there is no swap.
>> I can't even tell what you're expecting. Surely not that no pages are
>> ever evicted or flushed; your memory would fill up with page cache in no
time.
>
> Please do flush anytime, and do it in sync during OOMs; but don't
> evict procs especially not RUNNING procs, that is overkill.
Would you really like a system where once something was faulted in, it could
never leave? You'd run out of memory *awfully* fast.
}
Nix,
You should only fault if you have a place to fault to, as into a swap.
Without swap faulting is overkill.
Is it possible to change kswapd's default behaviour to not fault if there is
no swap?
Thanks!
next prev parent reply other threads:[~2005-06-28 13:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 20:04 Kswapd flaw Al Boldi
2005-06-27 15:58 ` Marcelo Tosatti
2005-06-28 6:37 ` Al Boldi
2005-06-28 8:18 ` Michal Schmidt
2005-06-28 9:08 ` Al Boldi
2005-06-28 9:54 ` Michal Schmidt
2005-06-28 10:50 ` Nix
2005-06-28 11:47 ` Al Boldi
2005-06-28 12:50 ` Nix
2005-06-28 13:52 ` Al Boldi [this message]
2005-06-28 14:37 ` Nix
2005-06-28 15:35 ` Al Boldi
2005-06-28 16:25 ` Nix
2005-06-28 18:15 ` Helge Hafting
2005-06-28 14:55 ` Paulo Marques
2005-06-28 9:58 ` Marcelo Tosatti
2005-06-28 16:43 ` Al Boldi
[not found] <4knRo-4Li-9@gated-at.bofh.it>
[not found] ` <4koWT-5Iy-21@gated-at.bofh.it>
2005-06-28 14:28 ` Robert Hancock
[not found] <20050628143932.GA14545@logos.cnet>
2005-06-29 4:53 ` Al Boldi
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=200506281352.QAA25851@raad.intranet \
--to=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nix@esperi.org.uk \
/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