From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Lance Yang <ioworker0@gmail.com>
Cc: <david@redhat.com>, <hannes@cmpxchg.org>, <linux-mm@kvack.org>,
<mhocko@kernel.org>, <roman.gushchin@linux.dev>,
<shakeel.butt@linux.dev>, <willy@infradead.org>
Subject: Re: [PATCH] mm: refactor folio_undo_large_rmappable()
Date: Thu, 16 May 2024 12:43:26 +0800 [thread overview]
Message-ID: <21b117a4-d869-436c-a939-cd48ba4e84f0@huawei.com> (raw)
In-Reply-To: <20240515065326.37970-1-ioworker0@gmail.com>
On 2024/5/15 14:53, Lance Yang wrote:
> Hi Kefeng,
>
>> In addtion, move all the checks into headfile to save a function call
>> for non-large-rmappable or empty deferred_list folio.
>
> s/addtion/addition
>
> And, IMO, 'headfile' looks a bit weird :)
> s/headfile/header file
Thanks, will fix them.
>
> Thanks,
> Lance
next prev parent reply other threads:[~2024-05-16 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 6:45 Kefeng Wang
2024-05-15 6:53 ` Lance Yang
2024-05-16 4:43 ` Kefeng Wang [this message]
2024-05-16 15:54 ` Vishal Moola
2024-05-17 5:18 ` Kefeng Wang
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=21b117a4-d869-436c-a939-cd48ba4e84f0@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=ioworker0@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--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