From: Ed Tomlinson <tomlins@cam.org>
To: Mike Galbraith <mikeg@wen-online.de>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Zlatko Calusic <zlatko.calusic@iskon.hr>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: Comment on patch to remove nr_async_pages limit
Date: Tue, 5 Jun 2001 07:42:28 -0400 [thread overview]
Message-ID: <01060507422800.28232@oscar> (raw)
In-Reply-To: <Pine.LNX.4.33.0106051140270.1227-100000@mikeg.weiden.de>
Hi,
To paraphase Mike,
We defer doing IO until we are under short of storage. Doing IO uses storage.
So delaying IO as much as we do forces us to impose limits. If we did the IO
earlier we would not need this limit often, if at all.
Does this make any sense?
Maybe we can have the best of both worlds. Is it possible to allocate the BH
early and then defer the IO? The idea being to make IO possible without having
to allocate. This would let us remove the async page limit but would ensure
we could still free.
Thoughts?
Ed Tomlinson
--
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 prev parent reply other threads:[~2001-06-05 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-05 1:04 Marcelo Tosatti
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 [this message]
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=01060507422800.28232@oscar \
--to=tomlins@cam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--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