From: David Hildenbrand <david@redhat.com>
To: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
Usama Arif <usamaarif642@gmail.com>
Cc: baolin.wang@linux.alibaba.com, chrisl@kernel.org,
hanchuanhua@oppo.com, ioworker0@gmail.com,
kaleshsingh@google.com, kasong@tencent.com,
linux-kernel@vger.kernel.org, ryan.roberts@arm.com,
v-songbaohua@oppo.com, ziy@nvidia.com, yuanshuai@oppo.com
Subject: Re: [PATCH v2 0/2] mm: collect the number of anon mTHP
Date: Mon, 19 Aug 2024 10:28:49 +0200 [thread overview]
Message-ID: <c817bf05-a9fa-4fb9-b8c6-a1de5a44e59a@redhat.com> (raw)
In-Reply-To: <CAGsJ_4yMu=aaQZEXtcwCdMgrxUuqQ-9P1AiqyyVLfehD_-my9A@mail.gmail.com>
On 18.08.24 09:58, Barry Song wrote:
> Hi Andrew, David, Usama,
>
> I'm attempting to rebase this series on top of Usama's
> [PATCH v3 0/6] mm: split underutilized THPs[1]
>
> However, I feel it is impossible and we might be tackling things
> in the wrong order.
Is just the ordering suboptimal (which can/will get resolved one way or
the other), or is there something fundamental that will make this series
here "impossible"?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-08-19 8:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 22:49 Barry Song
2024-08-11 22:49 ` [PATCH v2 1/2] mm: collect the number of anon large folios Barry Song
2024-08-21 21:34 ` David Hildenbrand
2024-08-22 0:52 ` Barry Song
2024-08-22 8:44 ` Barry Song
2024-08-22 8:59 ` David Hildenbrand
2024-08-22 9:21 ` Barry Song
2024-08-22 10:01 ` David Hildenbrand
2024-08-22 10:12 ` Barry Song
2024-08-11 22:49 ` [PATCH v2 2/2] mm: collect the number of anon large folios on split_deferred list Barry Song
2024-08-21 21:39 ` David Hildenbrand
2024-08-21 22:01 ` Barry Song
2024-08-21 22:10 ` David Hildenbrand
2024-08-18 7:58 ` [PATCH v2 0/2] mm: collect the number of anon mTHP Barry Song
2024-08-19 2:44 ` Usama Arif
2024-08-19 8:28 ` David Hildenbrand [this message]
2024-08-19 8:33 ` Barry Song
2024-08-19 8:52 ` Barry Song
2024-08-19 14:22 ` Usama Arif
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=c817bf05-a9fa-4fb9-b8c6-a1de5a44e59a@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=hanchuanhua@oppo.com \
--cc=ioworker0@gmail.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=usamaarif642@gmail.com \
--cc=v-songbaohua@oppo.com \
--cc=yuanshuai@oppo.com \
--cc=ziy@nvidia.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