From: David Hildenbrand <david@redhat.com>
To: Qi Zheng <zhengqi.arch@bytedance.com>,
the arch/x86 maintainers <x86@kernel.org>
Cc: hughd@google.com, willy@infradead.org, mgorman@suse.de,
muchun.song@linux.dev, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/7] synchronously scan and reclaim empty user PTE pages
Date: Sun, 7 Jul 2024 10:26:59 +0200 [thread overview]
Message-ID: <82ca055a-4b51-4db4-be7d-27b84aa70bd7@redhat.com> (raw)
In-Reply-To: <e7a8ddb2-52b5-4267-859b-e212644440b1@bytedance.com>
On 04.07.24 09:16, Qi Zheng wrote:
> Add the x86 mailing list that I forgot to CC before.
Hi,
I'm planning on looking into this (again, I'm very interested!), but
I'll be a bit (understatement) busy the next 1.5 weeks.
If I don't look into this within the next 3 weeks, an you please remind
me? Thanks!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-07-07 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 8:46 [RFC PATCH 0/7] synchronously scan and reclaim empty user PTE pages Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 1/7] mm: pgtable: make pte_offset_map_nolock() return pmdval Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 2/7] mm: introduce CONFIG_PT_RECLAIM Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 3/7] mm: pass address information to pmd_install() Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 4/7] mm: pgtable: try to reclaim empty PTE pages in zap_page_range_single() Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 5/7] x86: mm: free page table pages by RCU instead of semi RCU Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 6/7] x86: mm: define arch_flush_tlb_before_set_huge_page Qi Zheng
2024-07-01 8:46 ` [RFC PATCH 7/7] x86: select ARCH_SUPPORTS_PT_RECLAIM if X86_64 Qi Zheng
2024-07-04 7:16 ` [RFC PATCH 0/7] synchronously scan and reclaim empty user PTE pages Qi Zheng
2024-07-07 8:26 ` David Hildenbrand [this message]
2024-07-08 2:46 ` Qi Zheng
2024-07-26 9:07 ` Vlastimil Babka (SUSE)
2024-07-29 6:46 ` Qi Zheng
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=82ca055a-4b51-4db4-be7d-27b84aa70bd7@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=muchun.song@linux.dev \
--cc=willy@infradead.org \
--cc=x86@kernel.org \
--cc=zhengqi.arch@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).