public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-arch <linux-arch@vger.kernel.org>,
	Ira Weiny <ira.weiny@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: flush_dcache_page vs kunmap_local
Date: Thu, 4 Nov 2021 18:38:56 +0000	[thread overview]
Message-ID: <YYQowGK3oIAA5Yei@casper.infradead.org> (raw)
In-Reply-To: <CAHk-=wiKac4t-fOP_3fAf7nETfFLhT3ShmRmBq2J96y6jAr56Q@mail.gmail.com>

On Thu, Nov 04, 2021 at 08:30:55AM -0700, Linus Torvalds wrote:
> Why did this come up? Do you actually have some hardware or situation
> that cares?

Oh, we're doing review of the XFS/iomap folio patches, which led to
looking at zero_user_segments(), and I realised that memzero_page()
was now functionally identical to zero_user().  And you'd been quite
specific about not having flush_dcache_page() in there, so ... I wondered
if you'd had a change of mind.

  parent reply	other threads:[~2021-11-04 18:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:00 flush_dcache_page vs kunmap_local Matthew Wilcox
2021-11-04 15:30 ` Linus Torvalds
2021-11-04 16:54   ` Catalin Marinas
2021-11-04 17:08     ` Linus Torvalds
2021-11-04 18:04       ` Catalin Marinas
2021-11-04 18:20         ` Russell King (Oracle)
2021-11-04 18:23         ` Linus Torvalds
2021-11-05 19:40           ` Catalin Marinas
2021-11-04 18:38   ` Matthew Wilcox [this message]
2021-11-04 21:02     ` Linus Torvalds

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=YYQowGK3oIAA5Yei@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=ira.weiny@intel.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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