From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: mm: lazy cache flushing on non-mapped pages
Date: Wed, 22 May 2013 15:42:41 +0100 [thread overview]
Message-ID: <20130522144240.GA4173@localhost.cambridge.arm.com> (raw)
In-Reply-To: <1369223711-2995-1-git-send-email-ming.lei@canonical.com>
On Wed, May 22, 2013 at 12:55:11PM +0100, Ming Lei wrote:
> Currently flush_dcache_page() thinks pages as non-mapped if
> mapping_mapped(mapping) return false. This approach is very
> coase:
> - mmap on part of file may cause all pages backed on
> the file being thought as mmaped
>
> - file-backed pages aren't mapped into user space actually
> if the memory mmaped on the file isn't accessed
That's the meaning of mapping_mapped(), it doesn't tell whether the page
has a user virtual address.
> This patch also uses page_mapcount() to decide if the page has been
> mapped.
Better use page_mapped() instead.
--
Catalin
next prev parent reply other threads:[~2013-05-22 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 11:55 [RFC PATCH] ARM: mm: lazy cache flushing on non-mapped pages Ming Lei
2013-05-22 14:42 ` Catalin Marinas [this message]
2013-05-23 2:47 ` Ming Lei
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=20130522144240.GA4173@localhost.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).