From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Zlatko Calusic <zlatko.calusic@iskon.hr>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Comment on patch to remove nr_async_pages limit
Date: Mon, 4 Jun 2001 22:04:22 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0106042142550.2521-100000@freak.distro.conectiva> (raw)
Zlatko,
I've read your patch to remove nr_async_pages limit while reading an
archive on the web. (I have to figure out why lkml is not being delivered
correctly to me...)
Quoting your message:
"That artificial limit hurts both swap out and swap in path as it
introduces synchronization points (and/or weakens swapin readahead),
which I think are not necessary."
If we are under low memory, we cannot simply writeout a whole bunch of
swap data. Remember the writeout operations will potentially allocate
buffer_head's for the swapcache pages before doing real IO, which takes
_more memory_: OOM deadlock.
--
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-mm.org/
next reply other threads:[~2001-06-05 1:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 1:04 Marcelo Tosatti [this message]
2001-06-05 7:38 ` Mike Galbraith
2001-06-05 6:18 ` Marcelo Tosatti
2001-06-05 10:32 ` Mike Galbraith
2001-06-05 11:42 ` Ed Tomlinson
2001-06-05 16:08 ` Zlatko Calusic
2001-06-05 19:21 ` Benjamin C.R. LaHaise
2001-06-05 21:00 ` Comment on patch to remove nr_async_pages limitA Mike Galbraith
2001-06-05 22:21 ` Daniel Phillips
2001-06-05 16:05 ` Comment on patch to remove nr_async_pages limit Zlatko Calusic
2001-06-09 3:09 ` Rik van Riel
2001-06-09 6:07 ` Mike Galbraith
2001-06-05 15:57 ` Zlatko Calusic
2001-06-05 15:56 ` Zlatko Calusic
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.0106042142550.2521-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zlatko.calusic@iskon.hr \
/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