From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Mike Galbraith <mikeg@wen-online.de>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: Comment on patch to remove nr_async_pages limit
Date: 05 Jun 2001 18:08:45 +0200 [thread overview]
Message-ID: <87u21uykmq.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <01060507422800.28232@oscar> (Ed Tomlinson's message of "Tue, 5 Jun 2001 07:42:28 -0400")
Ed Tomlinson <tomlins@cam.org> writes:
[snip]
> 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.
>
Yes, this is a good idea if you ask me. Basically, to remove as many
limits as we can, and also to secure us from the deadlocks. With just
a few pages of extra memory for the reserved buffer heads, I think
it's a fair game. Still, pending further analysis...
--
Zlatko
--
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 16:08 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
2001-06-05 16:08 ` Zlatko Calusic [this message]
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=87u21uykmq.fsf@atlas.iskon.hr \
--to=zlatko.calusic@iskon.hr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=mikeg@wen-online.de \
--cc=tomlins@cam.org \
/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