From: "Juan J. Quintela" <quintela@fi.udc.es>
To: David Gibson <dgibson@linuxcare.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-fsdevel@vger.rutgers.edu, linux-kernel@vger.rutgers.edu,
linux-mm@kvack.org
Subject: Re: [PATCH] ramfs fixes
Date: 20 Jun 2000 13:57:36 +0200 [thread overview]
Message-ID: <yttd7lco98v.fsf@serpe.mitica> (raw)
In-Reply-To: David Gibson's message of "Tue, 20 Jun 2000 13:20:19 +1000"
>>>>> "david" == David Gibson <dgibson@linuxcare.com> writes:
Hi
david> This actually went in somewhat recently, in 2.3.99pre something (where
david> something is around 4 IIRC). This fixed a bug in ramfs, since
david> previously the dirty bit was never being cleared.
david> At the time ramfs was the *only* place using PG_dirty - it looked like
david> it was just a misleading name for something analagous to BH_protected.
david> Obviously that's not true any more. What does the PG_dirty bit mean
david> these days?
It means that the page is Dirty??? :)))))
Seriosly, now we can have dirty swap cache pages and soon dirty page
cache pages, coming from mmaped files, not only pages from Ramfs have
that bit set.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
--
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/
prev parent reply other threads:[~2000-06-20 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000619182802.B22551@tweedle.linuxcare.com.au>
2000-06-19 14:02 ` Rik van Riel
2000-06-20 3:20 ` David Gibson
2000-06-20 11:57 ` Juan J. Quintela [this message]
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=yttd7lco98v.fsf@serpe.mitica \
--to=quintela@fi.udc.es \
--cc=dgibson@linuxcare.com \
--cc=linux-fsdevel@vger.rutgers.edu \
--cc=linux-kernel@vger.rutgers.edu \
--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