linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: YoungJun Park <youngjun.park@lge.com>,
	ksummit@lists.linux.dev, chrisl@kernel.org, gunho.lee@lge.com,
	taejoon.song@lge.com, linux-mm@kvack.org,
	David Hildenbrand <david@redhat.com>
Subject: Re: [TECH TOPIC] Per-cgroup Swap Device Control
Date: Fri, 22 Aug 2025 13:10:22 -0400	[thread overview]
Message-ID: <20250822131022.4df59a60@gandalf.local.home> (raw)
In-Reply-To: <aKihqI8PWLFL1b5i@casper.infradead.org>

On Fri, 22 Aug 2025 17:58:16 +0100
Matthew Wilcox <willy@infradead.org> wrote:

> > Proposal:
> > I am developing on a restricted internal platform where there is a
> > technical requirement to use idle devices as extended memory.  
> 
> I don't think this is appropriate for the maintainer summit.  You
> can submit it to the Plumbers MM microconf [1] or LSFMM in May.
> 
> [1] https://lpc.events/event/19/contributions/1995/
> 
> Also you should have cc'd linux-mm for this kind of thing, adding
> it now.  Preserving the rest of the proposal for those who are
> interested.

From Ted's original email: https://lore.kernel.org/all/20250805144357.GA762104@mit.edu/

  Related to the Maintainer's Summit, the Kernel Summit is organized as a
  track which is run in parallel with the other tracks at the Linux
  Plumbers Conference (LPC), and is open to all registered attendees of
  LPC.  The goal of the Kernel Summit track will be to provide a forum to
  discuss specific technical issues that would be easier to resolve in
  person than over e-mail.  The program committee will also consider
  "information sharing" topics if they are clearly of interest to the wider
  development community (i.e., advanced training in topics that would be
  useful to kernel developers).

  To suggest a topic for the Kernel Summit, please do two things. by
  September 10th, 2025. First, please send e-mail with a subject prefix of
  [TECH TOPIC] to ksummit@lists.linux.dev.  As before, please use a
  separate e-mail for each topic.

So this appears to be appropriate.

-- Steve


  reply	other threads:[~2025-08-22 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aKgm+wisMipLqnL4@yjaykim-PowerEdge-T330>
2025-08-22 16:58 ` Matthew Wilcox
2025-08-22 17:10   ` Steven Rostedt [this message]
2025-08-22 17:43     ` Matthew Wilcox
2025-08-22 18:13       ` Chris Li
2025-08-22 18:26         ` Steven Rostedt
2025-08-23  0:42           ` YoungJun Park

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=20250822131022.4df59a60@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=gunho.lee@lge.com \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=taejoon.song@lge.com \
    --cc=willy@infradead.org \
    --cc=youngjun.park@lge.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