linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Ira Weiny <ira.weiny@intel.com>, <willy@infradead.org>,
	<linux-mm@kvack.org>
Subject: Re: [RFC PATCH 1/2] mm: remove duplicated flush_dcache_folio()
Date: Mon, 27 Feb 2023 14:14:00 +0800	[thread overview]
Message-ID: <d8ac7a79-474a-f20f-e636-9f5017ac9e00@intel.com> (raw)
In-Reply-To: <63fc43c9a56c1_3fa02943c@iweiny-mobl.notmuch>

Hi Ira,

On 2/27/2023 1:46 PM, Ira Weiny wrote:
> Yin Fengwei wrote:
>> folio_zero_range() calls the flush_dcache_folio() already. Remove
>> unnecessary flush_dcache_folio() call.
> 
> The change is probably reasonable but this statement is not exactly true.
> 
> The detail is that flush_dcache_page() is already called and another loop
> through the folio pages is unneeded.  Not to mention hiding these flush
> calls is nice because it is so hard to know when to use them.
Thanks again for checking the patch and sharing the comments.

Yes. This patch mainly focus on the unneeded dcache flush when I checked the
flush_dcache_folio() related code.


Regards
Yin, Fengwei

> 
>>
>> Signed-off-by: Yin Fengwei <fengwei.yin@intel.com>
>> ---
>>  fs/libfs.c | 1 -
>>  mm/shmem.c | 7 +------
>>  2 files changed, 1 insertion(+), 7 deletions(-)
>>
>> diff --git a/fs/libfs.c b/fs/libfs.c
>> index 4eda519c3002..d57370c8e382 100644
>> --- a/fs/libfs.c
>> +++ b/fs/libfs.c
>> @@ -543,7 +543,6 @@ EXPORT_SYMBOL(simple_setattr);
>>  static int simple_read_folio(struct file *file, struct folio *folio)
>>  {
>>  	folio_zero_range(folio, 0, folio_size(folio));
>> -	flush_dcache_folio(folio);
>>  	folio_mark_uptodate(folio);
>>  	folio_unlock(folio);
>>  	return 0;
>> diff --git a/mm/shmem.c b/mm/shmem.c
>> index 448f393d8ab2..66e50f0a15ab 100644
>> --- a/mm/shmem.c
>> +++ b/mm/shmem.c
>> @@ -1401,7 +1401,6 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)
>>  				goto redirty;
>>  		}
>>  		folio_zero_range(folio, 0, folio_size(folio));
>> -		flush_dcache_folio(folio);
>>  		folio_mark_uptodate(folio);
>>  	}
>>  
>> @@ -2010,11 +2009,7 @@ static int shmem_get_folio_gfp(struct inode *inode, pgoff_t index,
>>  	 * it now, lest undo on failure cancel our earlier guarantee.
>>  	 */
>>  	if (sgp != SGP_WRITE && !folio_test_uptodate(folio)) {
>> -		long i, n = folio_nr_pages(folio);
>> -
>> -		for (i = 0; i < n; i++)
>> -			clear_highpage(folio_page(folio, i));
>> -		flush_dcache_folio(folio);
>> +		folio_zero_range(folio, 0, folio_size(folio));
> 
> This is a separate optimization from what your cover letter explained.
> 
> Ira


  reply	other threads:[~2023-02-27  6:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 16:05 [RFC PATCH 0/2] minor cleanup of usage of flush_dcache_folio() Yin Fengwei
2023-02-16 16:05 ` [RFC PATCH 1/2] mm: remove duplicated flush_dcache_folio() Yin Fengwei
2023-02-27  5:46   ` Ira Weiny
2023-02-27  6:14     ` Yin, Fengwei [this message]
2023-02-16 16:05 ` [RFC PATCH 2/2] mm: add zero_user_folio_segments() Yin Fengwei
2023-02-16 19:19   ` Matthew Wilcox
2023-02-17  2:21     ` Yin, Fengwei
2023-02-27  5:31   ` Ira Weiny
2023-02-27  5:44     ` Yin, Fengwei

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=d8ac7a79-474a-f20f-e636-9f5017ac9e00@intel.com \
    --to=fengwei.yin@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=willy@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