linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	 Dave Hansen <dave.hansen@intel.com>,
	David Hildenbrand <david@redhat.com>,
	 Hugh Dickins <hughd@google.com>,
	James Houghton <jthoughton@google.com>,
	 Johannes Weiner <hannes@cmpxchg.org>,
	John Hubbard <jhubbard@nvidia.com>,
	 linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
	 Mel Gorman <mel.gorman@gmail.com>,
	Michal Hocko <mhocko@suse.com>,
	 Mike Kravetz <mike.kravetz@oracle.com>,
	 Mike Rapoport <mike.rapoport@gmail.com>,
	 Pasha Tatashin <tatashin@google.com>,
	Peter Xu <peterx@redhat.com>,
	 "Rao, Bharata Bhasker" <bharata@amd.com>,
	Rik van Riel <riel@surriel.com>,
	 Roman Gushchin <roman.gushchin@linux.dev>,
	 Shakeel Butt <shakeelb@google.com>,
	 "Shutemov, Kirill" <kirill.shutemov@intel.com>,
	Tejun Heo <tj@kernel.org>,  Vlastimil Babka <vbabka@suse.cz>,
	Yang Shi <shy828301@gmail.com>,  Zi Yan <ziy@nvidia.com>
Subject: [Invitation] Linux MM Alignment Session on HugeTLB Core MM Convergence on Wednesday
Date: Mon, 12 Jun 2023 19:01:16 -0700 (PDT)	[thread overview]
Message-ID: <c382b8a8-c259-815a-886b-e15628e27339@google.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]

Hi everybody,

We host a biweekly series, the Linux MM Alignment Session, on Wednesdays.
We'd like to invite MM developers to attend and will announce the topic
for the next instance on the Monday prior to the next meeting.

Our next Linux MM Alignment Session is scheduled for Wednesday.  The
details:

Wednesday, June 14 · 9:00 – 10:00am PDT (GMT-7)
https://meet.google.com/csb-wcds-xya
backup: (US) +1 347-682-5874 PIN: 356 962 072#
international: https://tel.meet/csb-wcds-xya?pin=1301132214803

This week's topic will be a technical brainstorming session on HugeTLB 
convergence with the core MM.  This has been discussed most recently in 
this thread: 
https://lore.kernel.org/linux-mm/ZIOEDTUBrBg6tepk@casper.infradead.org/T/

As discussed there, it would be useful to discuss areas where the HugeTLB 
subsystem could be unified with the core MM.  This includes both 
short-term and long-term objectives to improve reliability and 
maintainability:

 - Concrete areas where hugetlb and core MM can converge (pagewalks, for
   example)
 - Incremental progress on the above
 - Long-term plans for HugeTLB reservations
 - Anything other ideas?

This is intended to be for technical brainstorming, i.e. surface ideas 
where the HugeTLB subsystem and core MM could share a common framework and 
reduce HugeTLB's "special casing."

It would be great to align on common goals and discuss division of work as
well as timelines.

Also: if anybody has ideas for future topics, please let me know and I'll 
try to organize them.  We'd love to have volunteers to lead future topics 
as well as requests for MM topics to be presented.

Looking forward to seeing all of you on Wednesday!

             reply	other threads:[~2023-06-13  2:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  2:01 David Rientjes [this message]
     [not found] <c5afdf35-a5fa-03e2-348d-cf1d990fc389@google.com>
     [not found] ` <20230614230458.GB3559@monkey>
2023-06-15  1:12   ` David Rientjes
2023-06-15  8:04   ` Michal Hocko
2023-06-15  8:29     ` David Hildenbrand
2023-06-15 17:24       ` James Houghton
2023-06-15 18:58         ` Peter Xu
2023-06-15 18:31       ` Mike Kravetz
2023-06-15 17:00     ` James Houghton
2023-06-15 17:18       ` Matthew Wilcox
2023-06-15 17:59         ` Mike Kravetz

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=c382b8a8-c259-815a-886b-e15628e27339@google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=bharata@amd.com \
    --cc=dave.hansen@intel.com \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=jthoughton@google.com \
    --cc=kirill.shutemov@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=mel.gorman@gmail.com \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=mike.rapoport@gmail.com \
    --cc=peterx@redhat.com \
    --cc=riel@surriel.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeelb@google.com \
    --cc=shy828301@gmail.com \
    --cc=tatashin@google.com \
    --cc=tj@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --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