From: David Hildenbrand <david@redhat.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
"Yin, Fengwei" <fengwei.yin@intel.com>, Zi Yan <ziy@nvidia.com>,
Matthew Wilcox <willy@infradead.org>, Yu Zhao <yuzhao@google.com>,
David Rientjes <rientjes@google.com>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: Prerequisites for Large Anon Folios
Date: Thu, 31 Aug 2023 09:59:52 +0200 [thread overview]
Message-ID: <d6608a66-65ad-6162-d588-700a1ecbc38c@redhat.com> (raw)
In-Reply-To: <6e01c6fc-bbb7-47f5-9e2a-d476d2c3ef65@arm.com>
On 31.08.23 09:26, Ryan Roberts wrote:
> On 30/08/2023 17:20, David Hildenbrand wrote:
>> On 30.08.23 12:44, Ryan Roberts wrote:
>>> Hi All,
>>>
>>
>> Hi Ryan,
>>
>> I'll be back from vacation next Wednesday.
>>
>> Note that I asked David R. to have large anon folios as topic for the next
>> bi-weekly mm meeting.
>
> Ahh great! I don't have an invite to this meeting - is that something I can get
> added to?
I think David nowadays always sends out an invitation for Wednesday to
linux-mm on Monday or so. @David R., right? :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-08-31 8:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 9:41 Ryan Roberts
2023-07-23 12:33 ` Yin, Fengwei
2023-07-24 9:04 ` Ryan Roberts
2023-07-24 9:33 ` Yin, Fengwei
2023-07-24 9:46 ` Ryan Roberts
2023-07-24 9:54 ` Yin, Fengwei
2023-07-24 11:42 ` David Hildenbrand
2023-08-30 10:08 ` Ryan Roberts
2023-08-31 0:01 ` Yin, Fengwei
2023-08-31 7:16 ` Ryan Roberts
2023-08-30 10:44 ` Ryan Roberts
2023-08-30 16:20 ` David Hildenbrand
2023-08-31 7:26 ` Ryan Roberts
2023-08-31 7:59 ` David Hildenbrand [this message]
2023-08-31 9:04 ` Ryan Roberts
2023-09-01 14:44 ` David Hildenbrand
2023-09-04 10:06 ` Ryan Roberts
2023-09-05 20:54 ` David Rientjes
2023-08-31 0:08 ` Yin, Fengwei
2023-08-31 7:18 ` Ryan Roberts
2023-08-31 7:38 ` 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=d6608a66-65ad-6162-d588-700a1ecbc38c@redhat.com \
--to=david@redhat.com \
--cc=fengwei.yin@intel.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=ryan.roberts@arm.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.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