From: David Rientjes <rientjes@google.com>
To: Chris Li <chrisl@kernel.org>
Cc: David Hildenbrand <david@redhat.com>,
Daniel Gomez <da.gomez@samsung.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Barry Song <v-songbaohua@oppo.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Luis Chamberlain <mcgrof@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: Swap Min Odrer
Date: Wed, 8 Jan 2025 19:38:57 -0800 (PST) [thread overview]
Message-ID: <2eb1c8c3-1c45-f7cf-dd39-25a4a103e5dc@google.com> (raw)
In-Reply-To: <CACePvbXRzK5pomkAYs6VXd8qvWXWDN8BydxDPkD7H9kWPn11Qg@mail.gmail.com>
On Wed, 8 Jan 2025, Chris Li wrote:
> > Yeah, it would probably great to present the problem and the exact
> > constraints we have (e.g., things stupid me asks above regarding actual
> > sizes in which we can perform reads and writes), so we can discuss
> > possible solutions.
> >
> > @David R., is the slot in two weeks already taken?
>
> Hopefully I can send out the "virtual swapfile" proposal in time and
> we can discuss that as one of the possible approaches.
>
Thanks for this, this sounds like a great topic to pencil in for
Wednesday, January 22. We have two topics scheduled for the instances in
February so if we can't make the January 22 instance than the next session
would be March 5.
Chris: I'll follow-up with you offline for this to see if we can make it
happen.
Thanks!
next prev parent reply other threads:[~2025-01-09 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250107094349eucas1p1c973738624046458bbd8ca980cf6fe33@eucas1p1.samsung.com>
2025-01-07 9:43 ` Daniel Gomez
2025-01-07 10:31 ` David Hildenbrand
2025-01-07 12:29 ` Daniel Gomez
2025-01-07 16:41 ` David Hildenbrand
2025-01-08 14:14 ` Daniel Gomez
2025-01-08 20:36 ` David Hildenbrand
2025-01-08 21:19 ` Chris Li
2025-01-08 21:24 ` David Hildenbrand
2025-01-16 8:38 ` Chris Li
2025-01-20 12:02 ` David Hildenbrand
2025-01-09 3:38 ` David Rientjes [this message]
2025-01-08 21:09 ` Chris Li
2025-01-08 21:05 ` Chris Li
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=2eb1c8c3-1c45-f7cf-dd39-25a4a103e5dc@google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=da.gomez@samsung.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=ryan.roberts@arm.com \
--cc=v-songbaohua@oppo.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