From: Christoph Hellwig <hch@infradead.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: lsf-pc@lists.linux-foundation.org, SeongJae Park <sj@kernel.org>,
Minchan Kim <minchan@kernel.org>,
m.szyprowski@samsung.com, aneesh.kumar@kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
mina86@mina86.com, Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <liam.howlett@oracle.com>,
David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@kernel.org>, linux-mm <linux-mm@kvack.org>,
android-kernel-team <android-kernel-team@google.com>
Subject: Re: [LSF/MM/BPF TOPIC] Guaranteed CMA
Date: Mon, 3 Feb 2025 21:46:21 -0800 [thread overview]
Message-ID: <Z6GprV8hVi0I2_F2@infradead.org> (raw)
In-Reply-To: <CAJuCfpEWVEqsivd7oTvp4foEho_HaD1XNP8KTeKWzG_X2skfGQ@mail.gmail.com>
On Sat, Feb 01, 2025 at 04:19:25PM -0800, Suren Baghdasaryan wrote:
> Hi,
> I would like to discuss the Guaranteed Contiguous Memory Allocator
> (GCMA) mechanism that is being used by many Android vendors as an
> out-of-tree feature, collect input on its possible usefulness for
> others, feasibility to upstream and suggestions for possible better
> alternatives.
Well, start by having code on the list. We really need to stop all
these super hypothetical "wouldn't it be nice" discussions clogging up
the conferences.
next prev parent reply other threads:[~2025-02-04 5:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 0:19 [LSF/MM/BPF TOPIC] Guaranteed CMA Suren Baghdasaryan
2025-02-04 5:46 ` Christoph Hellwig [this message]
2025-02-04 7:47 ` Lorenzo Stoakes
2025-02-04 7:48 ` Christoph Hellwig
2025-02-04 9:03 ` Vlastimil Babka
2025-02-04 15:56 ` Suren Baghdasaryan
2025-02-04 8:18 ` David Hildenbrand
2025-02-04 11:23 ` Alexandru Elisei
2025-02-04 16:33 ` Suren Baghdasaryan
2025-03-20 18:06 ` Suren Baghdasaryan
2025-04-02 16:35 ` Suren Baghdasaryan
2025-08-22 22:14 ` Suren Baghdasaryan
2025-08-26 8:58 ` David Hildenbrand
2025-08-27 0:17 ` Suren Baghdasaryan
2025-09-01 16:01 ` David Hildenbrand
2025-10-10 1:30 ` Suren Baghdasaryan
2025-10-10 13:58 ` David Hildenbrand
2025-10-10 15:07 ` Suren Baghdasaryan
2025-10-10 15:37 ` David Hildenbrand
2025-10-10 15:47 ` Suren Baghdasaryan
2025-02-04 9:07 ` Vlastimil Babka
2025-02-04 16:20 ` Suren Baghdasaryan
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=Z6GprV8hVi0I2_F2@infradead.org \
--to=hch@infradead.org \
--cc=android-kernel-team@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=david@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=liam.howlett@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@kernel.org \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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.