From: Roger Larsson <roger.larsson@norran.net>
To: Rik van Riel <riel@conectiva.com.br>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [BUG?] kflushd launders without washing powder ???
Date: Sat, 21 Oct 2000 19:20:46 +0200 [thread overview]
Message-ID: <39F1D06E.5327CCB9@norran.net> (raw)
Hi,
I am still experimenting with the VM code.
During this exploration I stumbled into this code,
from kflushd in fs/buffer.c
flushed = flush_dirty_buffers(0);
if (free_shortage())
flushed += page_launder(GFP_BUFFER, 0);
a) GFP_BUFFER is __GFP_HIGH and __GFP_WAIT but not __GFP_IO
Trying to launder without washing powder???
Or is it somehow guaranteed that flushed buffers are from
the same pages?
Should a GFP_KFLUSHD be introduced - like GFP_KSWAPD ?
b) Where is no_of_inactive_dirty pages balanced against inactive_clean?
(I have to look some more at this - remove my own patches first...)
/RogerL
--
Home page:
http://www.norran.net/nra02596/
--
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/
reply other threads:[~2000-10-21 17:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=39F1D06E.5327CCB9@norran.net \
--to=roger.larsson@norran.net \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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