From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: avoid cache flushing in flush_dcache_page()
Date: Mon, 7 Nov 2016 12:00:06 +0000 [thread overview]
Message-ID: <20161107120005.xzjpsmpu5b6qs42v@localhost> (raw)
In-Reply-To: <20161107114845.GF1041@n2100.armlinux.org.uk>
On Mon, Nov 07, 2016 at 11:48:45AM +0000, Russell King - ARM Linux wrote:
> On Mon, Nov 07, 2016 at 11:35:27AM +0000, Catalin Marinas wrote:
> > On Mon, Nov 07, 2016 at 11:30:24AM +0100, Rabin Vincent wrote:
> > > diff --git a/arch/arm/mm/flush.c b/arch/arm/mm/flush.c
> > > index 3cced84..f1e6190 100644
> > > --- a/arch/arm/mm/flush.c
> > > +++ b/arch/arm/mm/flush.c
> > > @@ -327,6 +327,12 @@ void flush_dcache_page(struct page *page)
> > > if (page == ZERO_PAGE(0))
> > > return;
> > >
> > > + if (!cache_ops_need_broadcast() && cache_is_vipt_nonaliasing()) {
> > > + if (test_bit(PG_dcache_clean, &page->flags))
> > > + clear_bit(PG_dcache_clean, &page->flags);
> > > + return;
> > > + }
> > > +
> > > mapping = page_mapping(page);
> > >
> > > if (!cache_ops_need_broadcast() &&
> >
> > I'm ok with the logic in this patch but is there a way to combine the
> > two 'if' blocks together, just to keep the function shorter?
>
> Probably not without reducing code readability, or moving
> page_mapping() before this new if() block (which may introduce
> extra code into the path.)
You are right, we would need 'mapping' in the subsequent checks, so I
don't think the code would be more readable if we are to keep it
efficient. In this case:
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
prev parent reply other threads:[~2016-11-07 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 10:30 [PATCH] ARM: avoid cache flushing in flush_dcache_page() Rabin Vincent
2016-11-07 11:35 ` Catalin Marinas
2016-11-07 11:48 ` Russell King - ARM Linux
2016-11-07 12:00 ` Catalin Marinas [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=20161107120005.xzjpsmpu5b6qs42v@localhost \
--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