From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <linux-mm@kvack.org>, <akpm@linux-foundation.org>,
<kirill@shutemov.name>, <yuzhao@google.com>,
<ryan.roberts@arm.com>, <ying.huang@intel.com>
Subject: Re: [PATCH v3 2/2] lru: allow large batched add large folio to lru list
Date: Mon, 1 May 2023 13:52:24 +0800 [thread overview]
Message-ID: <38a38aa8-f291-946e-28c7-b27193e088fd@intel.com> (raw)
In-Reply-To: <ZE2bm1I/d+kbGBNF@casper.infradead.org>
Hi Matthew,
On 4/30/2023 6:35 AM, Matthew Wilcox wrote:
> On Sat, Apr 29, 2023 at 04:27:59PM +0800, Yin Fengwei wrote:
>> @@ -22,6 +23,7 @@ struct address_space;
>> struct pagevec {
>> unsigned char nr;
>> bool percpu_pvec_drained;
>> + unsigned short nr_pages;
>
> I still don't like storing nr_pages in the pagevec/folio_batch.
OK. Let me see whether I could find out other way without storing
the nr_pages. Thanks.
Regards
Yin, Fengwei
>
next prev parent reply other threads:[~2023-05-01 5:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 8:27 [PATCH v3 0/2] Reduce lock contention related with large folio Yin Fengwei
2023-04-29 8:27 ` [PATCH v3 1/2] THP: avoid lock when check whether THP is in deferred list Yin Fengwei
2023-05-04 11:48 ` kirill
2023-05-05 1:09 ` Yin, Fengwei
2023-05-29 2:58 ` Yin Fengwei
2023-05-05 0:52 ` Huang, Ying
2023-05-05 1:09 ` Yin, Fengwei
2023-04-29 8:27 ` [PATCH v3 2/2] lru: allow large batched add large folio to lru list Yin Fengwei
2023-04-29 22:35 ` Matthew Wilcox
2023-05-01 5:52 ` Yin, Fengwei [this message]
2023-05-05 5:51 ` Yin, Fengwei
2023-05-15 2:14 ` Yin, Fengwei
2023-06-20 3:22 ` Matthew Wilcox
2023-06-20 4:39 ` Yin Fengwei
2023-06-20 8:01 ` 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=38a38aa8-f291-946e-28c7-b27193e088fd@intel.com \
--to=fengwei.yin@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=yuzhao@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.