linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chris Li <chrisl@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	YoungJun Park <youngjun.park@lge.com>,
	ksummit@lists.linux.dev,  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 11:13:41 -0700	[thread overview]
Message-ID: <CACePvbUYp7w68C8z_TeMhOJQ0hmWw1jkwy+D_Lb+N5WbmufAug@mail.gmail.com> (raw)
In-Reply-To: <aKisJJYL9LV20qzg@casper.infradead.org>

On Fri, Aug 22, 2025 at 10:43 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Fri, Aug 22, 2025 at 01:10:22PM -0400, Steven Rostedt wrote:
> > 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.
>
> My mistake.  I thought tech topics were part of maintainer summit, not
> part of the kernel track.  It'll be up to the kernel track organiser(s)
> whether to accept it to that track or whether they think it'll be more
> appropriate in the MM microconf.

That is partly my fault as well. I suggest to YoungJun for the LPC
2025 in this email:

https://lore.kernel.org/linux-mm/CAF8kJuMo3yNKOZL9n5UkHx_O5cTZts287HOnQOu=KqQcnbrMdg@mail.gmail.com/

What I have in mind is extract as you said, the MM track Micro
Conference, and CC the linux-mm mail list as well. I forgot to mention
the details of the MM Micro Conference track part in my suggestion
email.

Anyway, is there any conflict to apply to LPC MM Micro Conference
track as well? Of course which conference to apply to is a decision
for YoungJun to make. I am just curious what options are available
now.

Hi, YoungJun,

If you decide to apply for LPC MM MC track as well, don't forget to
register yourself as a speaker on the LPC website.
https://lpc.events/event/19/abstracts/
The lower right of the page, there is a button "Submit a new abstract",
Click on that to start the process. Don't forget to select the pull
down menu MM Micro conference.

Hopefully see you in LPC then.

Chris


  reply	other threads:[~2025-08-22 18:13 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
2025-08-22 17:43     ` Matthew Wilcox
2025-08-22 18:13       ` Chris Li [this message]
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=CACePvbUYp7w68C8z_TeMhOJQ0hmWw1jkwy+D_Lb+N5WbmufAug@mail.gmail.com \
    --to=chrisl@kernel.org \
    --cc=david@redhat.com \
    --cc=gunho.lee@lge.com \
    --cc=ksummit@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --cc=rostedt@goodmis.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