data_type large_stringclasses 3
values | source large_stringclasses 29
values | code large_stringlengths 98 49.4M | filepath large_stringlengths 5 161 ⌀ | message large_stringclasses 234
values | commit large_stringclasses 234
values | subject large_stringclasses 418
values | critique large_stringlengths 101 1.26M ⌀ | metadata dict |
|---|---|---|---|---|---|---|---|---|
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Ownership of an mshare region is assigned to the process that creates
it. Establishing ownership ensures that accounting the memory in an
mshare region is applied to the owner and not spread among the processes
sharing the memory. It also provides a means for freeing mshare memory
in an OOM situation. Once an mshare ow... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:10 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | From: Khalid Aziz <khalid@kernel.org>
In preparation for enabling the handling of page faults in an mshare
region provide a way to link an mshare shared page table to a process
page table and otherwise find the actual vma in order to handle a page
fault. Implement an unmap_page_range vm_ops function for msharefs VMAs
... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:06 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | From: Khalid Aziz <khalid@kernel.org>
Reserve a range of ioctls for msharefs and add an ioctl for mapping
objects within an mshare region. The arguments are the same as mmap()
except that the start of the mapping is specified as an offset into
the mshare region instead of as an address. System-selected addresses
are n... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:11 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | The astute reader will notice that the code is largely copied from
ksys_mmap_pgoff() with key differences being that mapping an mshare
region within an mshare region is disallowed and that the possibly
modified size is checked to ensure the new mapping does not exceed
the bounds of the mshare region.
Signed-off-by: An... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:13 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | The arguments are the same as munmap() except that the start of the
mapping is specified as an offset into the mshare region instead of
as an address.
Signed-off-by: Anthony Yznaga <anthony.yznaga@oracle.com>
---
include/uapi/linux/msharefs.h | 7 +++++++
mm/mshare.c | 37 ++++++++++++++++++++++++++... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:12 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Add new mm flag, MMF_MSHARE.
Signed-off-by: Anthony Yznaga <anthony.yznaga@oracle.com>
---
include/linux/mm_types.h | 2 ++
mm/mshare.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index da5a7a31a81d..4586a3f384f1 100644
--- a/include/linux/mm_... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:14 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | When handling a fault in an mshare range, redirect charges for page
tables and other allocations to the mshare owner rather than the
current task.
Signed-off-by: Anthony Yznaga <anthony.yznaga@oracle.com>
---
mm/memory.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/mm/memory.c b/mm/memory.c
inde... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:04:15 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Memory pages shared between processes require page table entries
(PTEs) for each process. Each of these PTEs consume some of
the memory and as long as the number of mappings being maintained
is small enough, this space consumed by page tables is not
objectionable. When very few memory pages are shared between
processes... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:03:53 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | From: Khalid Aziz <khalid@kernel.org>
Make msharefs filesystem writable and allow creating directories
to support better access control to mshare'd regions defined in
msharefs.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signed-off-by: Anthony Yznaga <anthony.yznaga@oracle.com>
---
mm/mshare.c | 116 +++++++++++++... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 19 Aug 2025 18:03:56 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Hi Anthony,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on tip/sched/core trace/for-next tip/x86/core tip/x86/mm kees/for-next/execve linus/master v6.17-rc2 next-20250820]
[If your patch is applied to the wrong git tree, kindly dr... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 21 Aug 2025 03:02:57 +0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Hi Anthony,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on next-20250820]
[cannot apply to tip/sched/core trace/for-next tip/x86/core tip/x86/mm kees/for-next/execve linus/master v6.17-rc2]
[If your patch is applied to the wrong g... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 21 Aug 2025 04:36:46 +0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Hi Anthony,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[cannot apply to tip/sched/core trace/for-next tip/x86/core tip/x86/mm kees/for-next/execve linus/master v6.17-rc2]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submit... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 21 Aug 2025 23:40:42 +0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | * Anthony Yznaga <anthony.yznaga@oracle.com> [250819 21:04]:
Probably needs a new year or year range and another author?
I don't know the recovery here, but what about inode and inode link
count? | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Mon, 8 Sep 2025 14:29:55 -0400",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 20.08.25 03:03, Anthony Yznaga wrote:
Why can't we query the mapping instead?
--
Cheers
David / dhildenb | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Mon, 8 Sep 2025 20:45:28 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 20.08.25 03:04, Anthony Yznaga wrote:
That looks rather weird. I would have thought there would be an easy way
to query the mshare owner for a given mshare mapping, and if the current
MM corresponds to that owner you know that you are running in the owner
context.
Of course, we could have a helper like is_mshar... | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Mon, 8 Sep 2025 20:50:00 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 9/8/25 11:45 AM, David Hildenbrand wrote:
The bit check is nice and zippy since vma_is_mshare() is called for
every fault, but it's not required. The check could be made to be:
return vma->vm_ops == &msharefs_vm_ops; | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Mon, 8 Sep 2025 11:56:54 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 08.09.25 20:56, Anthony Yznaga wrote:
Yes, like we do in secretmem_mapping(), for example.
(there, we also have a vma_is_secretmem()).
--
Cheers
David / dhildenb | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Mon, 8 Sep 2025 21:02:03 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 9/8/25 11:29 AM, Liam R. Howlett wrote:
Yes. I'll make sure the next series is updated.
If d_make_root() returns NULL it will have called iput_final(inode)
which takes care of freeing the inode. | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Mon, 8 Sep 2025 12:09:40 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 9/8/25 11:50 AM, David Hildenbrand wrote:
I'm not quite following you. Charges for newly faulted pages will be
automatically directed to the mshare owner because the mshare mm will
have its mm_owner field pointing to the owner. On the other hand,
allocations for page table pages are handled differently.
GFP_PGT... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Mon, 8 Sep 2025 12:21:11 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 08.09.25 21:21, Anthony Yznaga wrote:
As a note, I think at some point we discussed re-routing page faults to
the owner, so the owner can take care of all of that naturally. Is that
what's happening here?
So, are we running into that code that we have current be another MM
than vma->vm_mm?
Reminds me of: FOLL... | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Mon, 8 Sep 2025 22:28:29 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 20.08.25 03:03, Anthony Yznaga wrote:
Regarding the overall design, two important questions:
In the context of this series, how do we handle VMA-modifying functions
like mprotect/some madvise/mlock/mempolicy/...? Are they currently
blocked when applied to a mshare VMA?
And how are we handling other page table w... | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Mon, 8 Sep 2025 22:32:22 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 9/8/25 1:28 PM, David Hildenbrand wrote:
The memcg charges are routed to the owner but otherwise the page faults
are handled using the mshare mm.
That will always be the case when handling a page fault in an mshare
region. The fault handling code uses the msharefs VMA to find the actual
VMA associated with the... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Mon, 8 Sep 2025 13:55:33 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Mon, Sep 08, 2025 at 10:32:22PM +0200, David Hildenbrand wrote:
I haven't been following this series recently, so I'm not sure what
Anthony will say. My expectation is that the shared VMA is somewhat
transparent to these operations; that is they are faulty if they span
the boundary of the mshare VMA, but otherwise... | {
"author": "Matthew Wilcox <willy@infradead.org>",
"date": "Mon, 8 Sep 2025 21:59:28 +0100",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 9/8/25 1:59 PM, Matthew Wilcox wrote:
I've received conflicting feedback in previous discussions that things
like protection changes should be done via ioctl. I do thing somethings
are appropriate for ioctl like map and unmap, but I also like the idea
of the existing APIs being transparent to mshare so long as t... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Mon, 8 Sep 2025 14:14:20 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 08.09.25 23:14, Anthony Yznaga wrote:
Right, I think there are (at least) two possible models.
(A) It's just a special file mapping.
How that special file is orchestrated is not controlled through VMA
change operations (mprotect etc) from one process but through dedicated
ioctl.
(B) It's something different.
... | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Tue, 9 Sep 2025 09:53:35 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 9/9/25 12:53 AM, David Hildenbrand wrote:
With respect to the current series there are some deficiencies. For
madvise(), there are some advices like MADV_DONTNEED that will operate
on the shared page table without taking the needed locks. Many will fail
for various reasons. I'll add a check to reject trying to a... | {
"author": "Anthony Yznaga <anthony.yznaga@oracle.com>",
"date": "Tue, 9 Sep 2025 11:29:20 -0700",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Tue, Sep 09, 2025 at 09:53:35AM +0200, David Hildenbrand wrote:
BTW I am 100% planning to take a look here and reply properly, just working
through a backlog atm :) [as usual :P]
Cheers, Lorenzo | {
"author": "Lorenzo Stoakes <lorenzo.stoakes@oracle.com>",
"date": "Tue, 9 Sep 2025 20:06:26 +0100",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Tue, Aug 19, 2025 at 06:03:54PM -0700, Anthony Yznaga wrote:
Welp. I really really don't like this API.
I assume this has been discussed previously, but why do we need a new
magical pseudofs mounted under some random /sys directory?
But, ok, assuming we're thinking about something hugetlbfs like, that's not too
ba... | {
"author": "Pedro Falcato <pfalcato@suse.de>",
"date": "Wed, 10 Sep 2025 13:14:13 +0100",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 10.09.25 14:14, Pedro Falcato wrote:
I don't remember the history (it's been a while) but there was this
interest of
(a) Sharing page tables for smaller files (not just PUD size etc.)
(b) Supporting also ordinary file systems, not just tmpfs
(c) Having a way to update protection of parts of a mapping and
i... | {
"author": "David Hildenbrand <david@redhat.com>",
"date": "Wed, 10 Sep 2025 14:46:45 +0200",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | Note there's some issue with this being applied to either mm-new or mm-unstable.
On Tue, Aug 19, 2025 at 06:04:06PM -0700, Anthony Yznaga wrote: | {
"author": "Lorenzo Stoakes <lorenzo.stoakes@oracle.com>",
"date": "Mon, 15 Sep 2025 16:27:36 +0100",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Tue, Aug 19, 2025 at 6:57 PM Anthony Yznaga
<anthony.yznaga@oracle.com> wrote:
Hi Anthony,
Thanks for continuing to push this forward, and apologies for joining
this discussion late. I am likely missing some context from the
various previous iterations of this feature, but I'd like to throw
another use case into t... | {
"author": "Kalesh Singh <kaleshsingh@google.com>",
"date": "Fri, 20 Feb 2026 13:35:58 -0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Fri, Feb 20, 2026 at 01:35:58PM -0800, Kalesh Singh wrote:
This can be solved by simply not using the Zygote model :p Or perhaps
MADV_DONTNEED/straight up unmapping libraries you don't need in the child's
side.
So, we've discussed this before. I initially liked this idea a lot more.
However, there are a couple of... | {
"author": "Pedro Falcato <pfalcato@suse.de>",
"date": "Sat, 21 Feb 2026 12:40:33 +0000",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Sat, Feb 21, 2026 at 4:40 AM Pedro Falcato <pfalcato@suse.de> wrote:
I think that's a separate topic, but that model is used on billions of
client devices :) The common runtime for apps and other core system
code is preloaded to significantly reduce app startup latencies.
Since we are interested in sharing text h... | {
"author": "Kalesh Singh <kaleshsingh@google.com>",
"date": "Mon, 23 Feb 2026 09:43:03 -0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 2/23/26 9:43 AM, Kalesh Singh wrote:
I haven't explored shared text, yet. There may be dragons there.
That would certainly help. sparc64 has a secondary context, but that
doesn't do us any good here. :-)
mshare won't support mapping objects in it with MAP_PRIVATE. Sharing
PTEs to memory that can be COW'd is... | {
"author": "anthony.yznaga@oracle.com",
"date": "Mon, 23 Feb 2026 11:55:06 -0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | All process must be aware of these special semantics.
I'd assume that fork() would simply replicate mshare region into the
fork'ed child process. So from that point of view, it's "transparent" as
in "no special mshare() handling required after fork".
--
Cheers,
David | {
"author": "\"David Hildenbrand (Arm)\" <david@kernel.org>",
"date": "Tue, 24 Feb 2026 10:40:30 +0100",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Mon, Feb 23, 2026 at 11:59 AM <anthony.yznaga@oracle.com> wrote:
I can see how mapping .text and .rodata as MAP_SHARED could
technically work, assuming the sharing process strictly mseals them to
guarantee they remain immutable. However, RELRO (.data.rel.ro) is a
different story. It must initially be mapped MAP_PRI... | {
"author": "Kalesh Singh <kaleshsingh@google.com>",
"date": "Wed, 25 Feb 2026 14:53:49 -0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Tue, Feb 24, 2026 at 1:40 AM David Hildenbrand (Arm)
<david@kernel.org> wrote:
Hi David,
That's agood point. If fork() simply replicates the mshare region, it
does achieve transparency in terms of setup.
I am still concerned about transparency in terms of observability.
Applications and sometimes inspect their o... | {
"author": "Kalesh Singh <kaleshsingh@google.com>",
"date": "Wed, 25 Feb 2026 15:06:10 -0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On 2/26/26 00:06, Kalesh Singh wrote:
The current plan is to have special "mshare container VMA" representing
an mshare region. What's actually hiding in there is defined in the
mshare MM.
One could, add support to walk the VMAs hiding in there instead; I don't
remember what out latest opinion about that was. But I do... | {
"author": "\"David Hildenbrand (Arm)\" <david@kernel.org>",
"date": "Thu, 26 Feb 2026 10:02:54 +0100",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Wed, Feb 25, 2026 at 03:06:10PM -0800, Kalesh Singh wrote:
I'm not worried about transparency because this is not supposed to be
transparent. This is not supposed to be used by most core system software.
This is supposed to help replace hugetlb page table sharing.
Transparent page table sharing has other constrain... | {
"author": "Pedro Falcato <pfalcato@suse.de>",
"date": "Thu, 26 Feb 2026 21:22:06 +0000",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | From: Khalid Aziz <khalid@kernel.org>
Users of mshare need to know the size and alignment requirement
for shared regions. Pre-populate msharefs with a file, mshare_info,
that provides this information. For now, pagetable sharing is
hardcoded to be at the PUD level.
Signed-off-by: Khalid Aziz <khalid@kernel.org>
Signe... | null | null | null | [PATCH v3 02/22] mm/mshare: pre-populate msharefs with information file | On Thu, Feb 26, 2026 at 1:22 PM Pedro Falcato <pfalcato@suse.de> wrote:
Hi Pedro,
Thanks for the detailed breakdown.
Firstly let me state that my goal definitely isn't to derail or block
the current mshare efforts. I'm mostly just trying to gather feedback
on what a "transparent", approach might actually look like.... | {
"author": "Kalesh Singh <kaleshsingh@google.com>",
"date": "Thu, 26 Feb 2026 22:34:56 -0800",
"is_openbsd": false,
"thread_id": "CAC_TJvdC+CSqvx+BvOv4gO2mJbwiBhb6OZO0sx=GXQ0CmA853g@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | This patch integrates the swap tier infrastructure with cgroup,
enabling the selection of specific swap devices per cgroup by
configuring allowed swap tiers.
The new `memory.swap.tiers` interface controls allowed swap tiers via a mask.
By default, the mask is set to include all tiers, allowing specific tiers to
be exc... | {
"author": "Youngjun Park <youngjun.park@lge.com>",
"date": "Mon, 26 Jan 2026 15:52:40 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | This patch connects swap devices to the swap tier infrastructure,
ensuring that devices are correctly assigned to tiers based on their
priority.
A `tier_mask` is added to identify the tier membership of swap devices.
Although tier-based allocation logic is not yet implemented, this
mapping is necessary to track which ... | {
"author": "Youngjun Park <youngjun.park@lge.com>",
"date": "Mon, 26 Jan 2026 15:52:39 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | This patch introduces the "Swap tier" concept, which serves as an
abstraction layer for managing swap devices based on their performance
characteristics (e.g., NVMe, HDD, Network swap).
Swap tiers are user-named groups representing priority ranges.
These tiers collectively cover the entire priority
space from -1 (`DEF... | {
"author": "Youngjun Park <youngjun.park@lge.com>",
"date": "Mon, 26 Jan 2026 15:52:38 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | This reverts commit 1b7e90020eb7 ("mm, swap: use percpu cluster as
allocation fast path").
Because in the newly introduced swap tiers, the global percpu cluster
will cause two issues:
1) it will cause caching oscillation in the same order of different si
if two different memcg can only be allowed to access differen... | {
"author": "Youngjun Park <youngjun.park@lge.com>",
"date": "Mon, 26 Jan 2026 15:52:41 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | When using per-device percpu clusters (instead of a global one),
a naive allocation logic triggers swap device rotation on every
allocation. This behavior leads to severe fragmentation and performance
regression.
To address this, this patch introduces a per-cpu cache for the swap
device. The allocation logic is update... | {
"author": "Youngjun Park <youngjun.park@lge.com>",
"date": "Mon, 26 Jan 2026 15:52:42 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | Hi Youngjun,
On Sun, Jan 25, 2026 at 10:53 PM Youngjun Park <youngjun.park@lge.com> wrote:
Thanks for the patches series.
Sorry for the late reply. I have been wanting to reply to it but get
super busy at work.
Some high level feedback for the series. Now that you demonstrated the
whole series, let's focus on makin... | {
"author": "Chris Li <chrisl@kernel.org>",
"date": "Wed, 11 Feb 2026 22:12:04 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Sun, Jan 25, 2026 at 11:08 PM Youngjun Park <youngjun.park@lge.com> wrote:
One idea is that, instead of using percpu per swap device.
You can make the global percpu cluster per tier. Because the max tier
number is smaller than the max number of swap devices. That is likely
a win.
Chris | {
"author": "Chris Li <chrisl@kernel.org>",
"date": "Wed, 11 Feb 2026 23:37:55 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | Hi Yongjun,
On Sun, Jan 25, 2026 at 10:53 PM Youngjun Park <youngjun.park@lge.com> wrote:
This function can use some simplification to make the indentation flater.
We can have a CONFIG option for the MAX_SWAPTIER. I think the default
should be a small number like 4.
When we add, modify, remove a tier. The simple ... | {
"author": "Chris Li <chrisl@kernel.org>",
"date": "Thu, 12 Feb 2026 01:07:45 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Wed, Feb 11, 2026 at 10:12 PM Chris Li <chrisl@kernel.org> wrote:
Just take a quick look at the series. I take that suggestion back.
This series is actually not too long. Adding the tiers name alone does
not add any real value. I actually need to look at the whole series
rather than just the tier name alone.
Chris | {
"author": "Chris Li <chrisl@kernel.org>",
"date": "Thu, 12 Feb 2026 01:22:04 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Sun, Jan 25, 2026 at 10:53 PM Youngjun Park <youngjun.park@lge.com> wrote:
This comment seems a bit clunky to me. The "+" is removed, as noted
above, but then why are we saying "even if a child re-enables a tier
with "+"" here? Am I missing something?
But otherwise, I assume you mean to restrict child's allowed s... | {
"author": "Nhat Pham <nphamcs@gmail.com>",
"date": "Thu, 12 Feb 2026 09:57:40 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | Hi Youngjun,
On Mon, Jan 26, 2026 at 03:52:37PM +0900, Youngjun Park wrote:
One of the LPC feedback you missed is to not add memcg interface for
this functionality and explore BPF way instead.
We are normally very conservative to add new interfaces to cgroup.
However I am not even convinced that memcg interface is t... | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Thu, 12 Feb 2026 10:33:22 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Wed, Feb 11, 2026 at 10:12:04PM -0800, Chris Li wrote:
Hi Chris,
Thank you for the direction.
I agree that breaking the series into smaller, mergeable steps is the
right approach. However, since introducing the definitions alone might
lack immediate usage, I propose a slightly
modified roadmap to ensure Step 1 de... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 13 Feb 2026 10:59:38 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Thu, Feb 12, 2026 at 01:07:45AM -0800, Chris Li wrote:
Agreed. I will refactor this to flatten the indentation.
Sounds good. I will add a CONFIG option for it and ensure it doesn't exceed
MAX_SWAPFILE.
I have given this a lot of thought.
Since the current interface allows mixing add (+), remove (-), and modi... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 13 Feb 2026 11:18:05 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Thu, Feb 12, 2026 at 01:22:04AM -0800, Chris Li wrote:
Oops, I replied to your previous email before seeing this one.
Stripping out the remove/modify parts is also feasible. Do you agree with
that direction?
Youngjun | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 13 Feb 2026 11:26:19 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Thu, Feb 12, 2026 at 09:57:40AM -0800, Nhat Pham wrote:
To clarify, previously, the default state used all tiers. Using "+"
switched to "an exclusive mode" where only that specific tier was used.
I am changing ... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 13 Feb 2026 11:43:37 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Thu, Feb 12, 2026 at 10:33:22AM -0800, Shakeel Butt wrote:
Apologies for overlooking the feedback regarding the BPF approach. Thank you
for the suggestion.
I agree that using BPF would provide greater flexibility, allowing control not
just at the memcg level, but also per-process or for complex workloads.
(As like... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 13 Feb 2026 12:58:40 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Thu, Feb 12, 2026 at 01:07:45AM -0800, Chris Li wrote:
I missed one comment.
The tier of existing swapfiles is immutable once assigned at swapon.
I removed tier reference.
Instead of reference counting, each operation validates the tier
range at operation time to guarantee this invariant.
- add: Does not chan... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 13 Feb 2026 23:33:35 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | Please don't send a new version of the series before concluding the discussion
on the previous one.
On Fri, Feb 13, 2026 at 12:58:40PM +0900, YoungJun Park wrote:
No need for apologies. These things take time and multiple iterations.
Yes it provides the flexibility but that is not the main reason I am pushing for
i... | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Fri, 20 Feb 2026 19:47:22 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Fri, Feb 20, 2026 at 7:47 PM Shakeel Butt <shakeel.butt@linux.dev> wrote:
In this case I think it is fine. You haven't responded to YoungJun's
last response in over a week. He might have mistaken that the
discussion concluded.
Consider it is one of the iterations. It is hard enough to contribute
to the kernel. Rel... | {
"author": "Chris Li <chrisl@kernel.org>",
"date": "Fri, 20 Feb 2026 22:07:44 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Fri, Feb 20, 2026 at 07:47:22PM -0800, Shakeel Butt wrote:
Understood. Let's continue the discussion. :D
Chris has already provided a thorough response, but I would like to
add my perspective as well.
I understand your concern about committing to a stable interface too
early. As Chris suggested, we could reduce ... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Sat, 21 Feb 2026 23:30:59 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Fri, Feb 20, 2026 at 10:07:44PM -0800, Chris Li wrote:
[...]
No, that is secondary because I am not seeing the real use-case of
controlling/partitioning swap devices among sub-workloads. Until that is
figured out, adding a stable API is not good.
I am assuming you meant Google and particularly Prodkernel team and... | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Sat, 21 Feb 2026 09:44:01 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Sat, Feb 21, 2026 at 09:44:01AM -0800, Shakeel Butt wrote:
....
After reading the reply and re-think more of it.
I have a few questions regarding the BPF-first approach you
suggested, if you don't mind. Some of them I am re-asking
because I feel they have not been clearly addressed yet.
- We are in an embedded en... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Sun, 22 Feb 2026 10:16:04 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | Hi YoungJun,
I see you have sent a separate email on BPF specific questions to which I will
respond separately, here I will respond to other questions/comments.
On Sat, Feb 21, 2026 at 11:30:59PM +0900, YoungJun Park wrote:
[...]
If you don't mind, can you share a bit more about the cgroup hierarchy structure
of you... | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Sun, 22 Feb 2026 21:56:13 -0800",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | This is the second version of the RFC for the "Swap Tiers" concept.
Link to v1: https://lore.kernel.org/linux-mm/20251109124947.1101520-1-youngjun.park@lge.com/
This version incorporates feedback received during LPC 2025 and addresses
comments from the previous review. We have also included experimental
results based ... | null | null | null | [RFC PATCH v2 0/5] mm/swap, memcg: Introduce swap tiers for cgroup based swap control | On Sun, Feb 22, 2026 at 09:56:13PM -0800, Shakeel Butt wrote:
While I await your response on the other thread,
I thought I would answer these questions first :)
We are primarily targeting Cgroup v2 at now.
That is correct; the swap priority behavior remains unchanged.
While this is slightly tangential, I see a ... | {
"author": "YoungJun Park <youngjun.park@lge.com>",
"date": "Fri, 27 Feb 2026 11:43:50 +0900",
"is_openbsd": false,
"thread_id": "aaEE5kdAgcRcBheY@yjaykim-PowerEdge-T330.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | vma_expand() error handling is a bit confusing with "if (ret) return ret;"
mixed with "if (!ret && ...) ret = ...;". Simplify the code to check
for errors and return immediately after an operation that might fail.
This also makes later changes to this function more readable.
No functional change intended.
Suggested-b... | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Wed, 25 Feb 2026 23:06:07 -0800",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patch:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. proces... | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Wed, 25 Feb 2026 23:06:08 -0800",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | Replace vma_start_write() with vma_start_write_killable() when
process_vma_walk_lock() is used with PGWALK_WRLOCK option.
Adjust its direct and indirect users to check for a possible error
and handle it. Ensure users handle EINTR correctly and do not ignore
it.
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---... | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Wed, 25 Feb 2026 23:06:09 -0800",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | * Suren Baghdasaryan <surenb@google.com> [260226 02:06]:
This looks the same as v2, so I'll try again ;)
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com> | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Thu, 26 Feb 2026 11:42:27 -0500",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | On Thu, Feb 26, 2026 at 8:43 AM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
Sorry, missed adding it. So again, thank you very much! | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Thu, 26 Feb 2026 09:23:19 -0800",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | * Suren Baghdasaryan <surenb@google.com> [260226 02:06]:
Some nits below, but lgtm.
Reviewed-by: Liam R. Howlett <Liam.Howlett@oracle.com>
Could avoid allocating here by reordering the lock, but this is fine.
Ditto here, ordering would mean no freeing.
There's no way this is going to fail, right?
I'd rather h... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Thu, 26 Feb 2026 12:43:08 -0500",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | On Wed, 25 Feb 2026 23:06:09 -0800
Suren Baghdasaryan <surenb@google.com> wrote:
can you very briefly explain how we can end up with -EINTR here?
do I understand correctly that -EINTR is possible here only if the
process is being killed?
[...] | {
"author": "Claudio Imbrenda <imbrenda@linux.ibm.com>",
"date": "Thu, 26 Feb 2026 19:10:07 +0100",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | On Thu, Feb 26, 2026 at 10:10 AM Claudio Imbrenda
<imbrenda@linux.ibm.com> wrote:
Correct, it would happen if the process has a pending fatal signal
(like SIGKILL) in its signal queue. | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Thu, 26 Feb 2026 10:24:49 -0800",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | On Thu, Feb 26, 2026 at 9:43 AM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
Thanks!
Ack. I'll move it before vma_iter_prealloc().
Ack. Will move.
You are technically correct but this is only true because of how
vma_start_write_killable() is implemented, so it's a technical detail
of the implementation, whic... | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Thu, 26 Feb 2026 13:44:47 -0800",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Now that we have vma_start_write_killable() we can replace most of the
vma_start_write() calls with it, improving reaction time to the kill
signal.
There are several places which are left untouched by this patchset:
1. free_pgtables() because function should free page tables even if a
fatal signal is pending.
2. use... | null | null | null | [PATCH v3 0/3] Use killable vma write locking in most places | On Thu, 26 Feb 2026 10:24:49 -0800
Suren Baghdasaryan <surenb@google.com> wrote:
Acked-by: Claudio Imbrenda <imbrenda@linux.ibm.com> | {
"author": "Claudio Imbrenda <imbrenda@linux.ibm.com>",
"date": "Fri, 27 Feb 2026 09:57:14 +0100",
"is_openbsd": false,
"thread_id": "CAJuCfpExatqPmdzSzRupURQ84Cme3JBT2gPvAS3WmK0G24xnPA@mail.gmail.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | Hi,
I previously sent a similar email which unfortunately had encoding issues.
I'm resending a cleaned-up version here so it's easier to read and discuss.
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shi... | {
"author": "wangzicheng <wangzicheng@honor.com>",
"date": "Tue, 24 Feb 2026 03:17:07 +0000",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | On Mon, Feb 23, 2026 at 7:17 PM wangzicheng <wangzicheng@honor.com> wrote:
For obvious reasons I'm interested in this discussion. We also notice
some shortcomings of MGLRU and would like to collaborate on resolving
them.
Thanks,
Suren. | {
"author": "Suren Baghdasaryan <surenb@google.com>",
"date": "Tue, 24 Feb 2026 09:10:45 -0800",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | On Tue, Feb 24, 2026 at 11:17 AM wangzicheng <wangzicheng@honor.com> wrote:
One fundamental design of MGLRU is that file generations and anon
generations catch up with each other when the generation gap reaches
two or more. As a result, even if swappiness is set very high, its
effect on aggressively reclaiming anonymo... | {
"author": "Barry Song <21cnbao@gmail.com>",
"date": "Wed, 25 Feb 2026 04:23:38 +0800",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | Hi Barry,
Thanks for the detailed feedback and observations.
We also feel this direction might be more reasonable.
Yes.
Yes, we’ve identified the exact code locations where this happens:
in slow path
static bool throttle_direct_reclaim(gfp_t gfp_mask, struct zonelist *zonelist,
nodemask_t *nodemask)... | {
"author": "wangzicheng <wangzicheng@honor.com>",
"date": "Wed, 25 Feb 2026 10:43:42 +0000",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | On Wed, Feb 25, 2026 at 2:46 AM wangzicheng <wangzicheng@honor.com> wrote:
Hi Zicheng,
I would be very interested in joining this discussion at LSF/MM as well.
I actually just replied to Kairui's MGLRU thread noting some similar
observations we've made while evaluating MGLRU [1]. I think your
findings in Q3 regardin... | {
"author": "Kalesh Singh <kaleshsingh@google.com>",
"date": "Wed, 25 Feb 2026 18:04:11 -0800",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | On Wed, Feb 25, 2026 at 6:43 PM wangzicheng <wangzicheng@honor.com> wrote:
[...]
Thanks. I understand it could be problematic if throttling occurs,
especially on threads related to user experience.
We might be able to leverage some existing infrastructure. MGLRU
maintains an LRU of LRUs, and within this structure, i... | {
"author": "Barry Song <21cnbao@gmail.com>",
"date": "Thu, 26 Feb 2026 16:03:08 +0800",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | Hi Kalesh,
Thanks for following up and for sharing your observations.
For Q3, we have only tried some approaches so far and don’t have a solid solution yet.
We’d be happy to share our field data and some Perfetto traces. We believe it would
be very helpful to discuss with you and Kairui at LSF/MM/BPF.
Best,
... | {
"author": "wangzicheng <wangzicheng@honor.com>",
"date": "Thu, 26 Feb 2026 13:06:11 +0000",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | Thank you for the detailed following up.
For Q3, the throttling is dangerous for UX‑critical threads. Kalesh also shared similar
observations about long direct reclaim tail latencies.
Regarding the LRU‑of‑LRUs idea, that does sound like a promising direction
(compare to vendor hook).
but it seems hardly suppo... | {
"author": "wangzicheng <wangzicheng@honor.com>",
"date": "Thu, 26 Feb 2026 13:29:40 +0000",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | Hi Barry and Zicheng,
On Tue, Feb 24, 2026 at 2:23 PM Barry Song <21cnbao@gmail.com> wrote:
To provide some context, the file and anon generations are coupled
primarily to simplify the MGLRU logic (Original Yu Zhao's intent).
Separating the two should allow for more flexible policies for sure.
Pardon my lack of fam... | {
"author": "Yuanchu Xie <yuanchu@google.com>",
"date": "Thu, 26 Feb 2026 16:10:59 -0600",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | On Thu, Feb 26, 2026 at 2:11 PM Yuanchu Xie <yuanchu@google.com> wrote:
I think he means that whichever memcg is next up on the memcg LRU is
the one that gets reclaimed from first, regardless of whether that
memcg is for a foreground app. Because there is currently no strong
relationship between memcg LRU ordering and... | {
"author": "\"T.J. Mercier\" <tjmercier@google.com>",
"date": "Thu, 26 Feb 2026 16:13:17 -0800",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Hi,
MGLRU has been available on Android for about four years, but many
OEM vendors still choose not to enable it in production.
HONOR is a major Android OEM shipping tens of millions of devices
per year, and we run MGLRU on all our devices across multiple kernel
versions (5.15~6.12) and RAM configurations(4G~24G... | null | null | null | [LSF/MM/BPF TOPIC] MGLRU on Android: Real-World Problems and
Challenges | Hi T.J.,
Yes, exactly.
That sounds good to me. We're also experimenting with a similar approach.
In my opinion, these knobs are a good opportunity to combine some ML
and autotuning (in userspace, not in kernel space as the kernel-ML
patches did):
- explore a reasonable memory.low / memory.high range for a g... | {
"author": "wangzicheng <wangzicheng@honor.com>",
"date": "Fri, 27 Feb 2026 10:03:11 +0000",
"is_openbsd": false,
"thread_id": "2e1aea6dec5849fda1c9bfffc58f9be0@honor.com.mbox.gz"
} |
lkml_critique | linux-mm | Track page access/dirty status in gem-shmem for better integration with
the overall memory management. Gem-shmem has long had two flag bits in
struct drm_gem_shmem_object, named pages_mark_accessed_on_put and
pages_mark_dirty_on_put, but never used them much; except for some odd
cases in drivers. Therefore pages in gem... | null | null | null | [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status | Replace shmem->base with obj in several places. It is the same value,
but the latter is easier to read.
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
---
drivers/gpu/drm/drm_gem_shmem_helper.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(... | {
"author": "Thomas Zimmermann <tzimmermann@suse.de>",
"date": "Fri, 27 Feb 2026 12:42:06 +0100",
"is_openbsd": false,
"thread_id": "20260227114509.165572-3-tzimmermann@suse.de.mbox.gz"
} |
lkml_critique | linux-mm | Track page access/dirty status in gem-shmem for better integration with
the overall memory management. Gem-shmem has long had two flag bits in
struct drm_gem_shmem_object, named pages_mark_accessed_on_put and
pages_mark_dirty_on_put, but never used them much; except for some odd
cases in drivers. Therefore pages in gem... | null | null | null | [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status | On successful vmap, set the page_mark_accessed_on_put and _dirty_on_put
flags in the gem-shmem object. Signals that the contained pages require
LRU and dirty tracking when they are being released back to SHMEM. Clear
these flags on put, so that the buffer remains quiet until the next call
to vmap. There's no means of h... | {
"author": "Thomas Zimmermann <tzimmermann@suse.de>",
"date": "Fri, 27 Feb 2026 12:42:11 +0100",
"is_openbsd": false,
"thread_id": "20260227114509.165572-3-tzimmermann@suse.de.mbox.gz"
} |
lkml_critique | linux-mm | Track page access/dirty status in gem-shmem for better integration with
the overall memory management. Gem-shmem has long had two flag bits in
struct drm_gem_shmem_object, named pages_mark_accessed_on_put and
pages_mark_dirty_on_put, but never used them much; except for some odd
cases in drivers. Therefore pages in gem... | null | null | null | [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status | Not having a page pointer in the mmap fault handler is an error. Test
for this situation and return VM_FAULT_SIGBUS if so. Also replace several
lookups of the page with a local variable.
Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
---
drivers/gpu... | {
"author": "Thomas Zimmermann <tzimmermann@suse.de>",
"date": "Fri, 27 Feb 2026 12:42:07 +0100",
"is_openbsd": false,
"thread_id": "20260227114509.165572-3-tzimmermann@suse.de.mbox.gz"
} |
lkml_critique | linux-mm | Track page access/dirty status in gem-shmem for better integration with
the overall memory management. Gem-shmem has long had two flag bits in
struct drm_gem_shmem_object, named pages_mark_accessed_on_put and
pages_mark_dirty_on_put, but never used them much; except for some odd
cases in drivers. Therefore pages in gem... | null | null | null | [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status | Return the exact VM_FAULT_ mask from drm_gem_shmem_try_map_pmd(). Gives
the caller better insight into the result. Return 0 if nothing was done.
If the caller sees VM_FAULT_NOPAGE, drm_gem_shmem_try_map_pmd() added a
PMD entry to the page table. As before, return early from the page-fault
handler in that case.
Signed... | {
"author": "Thomas Zimmermann <tzimmermann@suse.de>",
"date": "Fri, 27 Feb 2026 12:42:08 +0100",
"is_openbsd": false,
"thread_id": "20260227114509.165572-3-tzimmermann@suse.de.mbox.gz"
} |
lkml_critique | linux-mm | Track page access/dirty status in gem-shmem for better integration with
the overall memory management. Gem-shmem has long had two flag bits in
struct drm_gem_shmem_object, named pages_mark_accessed_on_put and
pages_mark_dirty_on_put, but never used them much; except for some odd
cases in drivers. Therefore pages in gem... | null | null | null | [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status | The current mmap page-fault handler requires some changes before it
can track folio access.
Call to folio_test_pmd_mappable() into the mmap page-fault handler
before calling drm_gem_shmem_try_map_pmd(). The folio will become
useful for tracking the access status.
Also rename drm_gem_shmem_try_map_pmd() to _try_insert... | {
"author": "Thomas Zimmermann <tzimmermann@suse.de>",
"date": "Fri, 27 Feb 2026 12:42:09 +0100",
"is_openbsd": false,
"thread_id": "20260227114509.165572-3-tzimmermann@suse.de.mbox.gz"
} |
lkml_critique | linux-mm | Track page access/dirty status in gem-shmem for better integration with
the overall memory management. Gem-shmem has long had two flag bits in
struct drm_gem_shmem_object, named pages_mark_accessed_on_put and
pages_mark_dirty_on_put, but never used them much; except for some odd
cases in drivers. Therefore pages in gem... | null | null | null | [PATCH v4 0/6] drm/gem-shmem: Track page accessed/dirty status | Invoke folio_mark_accessed() in mmap page faults to add the folio to
the memory manager's LRU list. Userspace invokes mmap to get the memory
for software rendering. Compositors do the same when creating the final
on-screen image, so keeping the pages in LRU makes sense. Avoids paging
out graphics buffers when under mem... | {
"author": "Thomas Zimmermann <tzimmermann@suse.de>",
"date": "Fri, 27 Feb 2026 12:42:10 +0100",
"is_openbsd": false,
"thread_id": "20260227114509.165572-3-tzimmermann@suse.de.mbox.gz"
} |
lkml_critique | linux-mm | Add a new DAMON sysfs interface file, namely goal_tuner under the DAMOS
quotas directory. It is connected to the damos_quota->goal_tuner field.
Users can therefore select their favorite goal-based quotas tuning
algorithm by writing special keywords to the file.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/dam... | null | null | null | [RFC PATCH 3/5] mm/damon/sysfs-schemes: implement quotas->goal_tuner file | Currently DAMOS quota goal feature utilizes a single feedback loop based
algorithm for automatic tuning of the effective quota. It is proven to
be useful on dynamic environments that operate systems with only
kernels. But, no one fits all, and we got multiple reports [1,2] of
cases that the algorithm is not optimum.
... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Wed, 11 Feb 2026 22:23:08 -0800",
"is_openbsd": false,
"thread_id": "20260227015613.91346-1-sj@kernel.org.mbox.gz"
} |
lkml_critique | linux-mm | Add a new DAMON sysfs interface file, namely goal_tuner under the DAMOS
quotas directory. It is connected to the damos_quota->goal_tuner field.
Users can therefore select their favorite goal-based quotas tuning
algorithm by writing special keywords to the file.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/dam... | null | null | null | [RFC PATCH 3/5] mm/damon/sysfs-schemes: implement quotas->goal_tuner file | Document the newly added goal-based quota tuner selection feature.
Provide the list of the available tuner with descriptions of their
behaviors and when those can be used.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
Documentation/mm/damon/design.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Wed, 11 Feb 2026 22:23:11 -0800",
"is_openbsd": false,
"thread_id": "20260227015613.91346-1-sj@kernel.org.mbox.gz"
} |
lkml_critique | linux-mm | Add a new DAMON sysfs interface file, namely goal_tuner under the DAMOS
quotas directory. It is connected to the damos_quota->goal_tuner field.
Users can therefore select their favorite goal-based quotas tuning
algorithm by writing special keywords to the file.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/dam... | null | null | null | [RFC PATCH 3/5] mm/damon/sysfs-schemes: implement quotas->goal_tuner file | Update the DAMON usage document for the new sysfs file for the goal
based quota auto-tuning, 'goal_tuner'.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
Documentation/admin-guide/mm/damon/usage.rst | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/Documentation/admin-guide/mm/da... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Wed, 11 Feb 2026 22:23:12 -0800",
"is_openbsd": false,
"thread_id": "20260227015613.91346-1-sj@kernel.org.mbox.gz"
} |
lkml_critique | linux-mm | Add a new DAMON sysfs interface file, namely goal_tuner under the DAMOS
quotas directory. It is connected to the damos_quota->goal_tuner field.
Users can therefore select their favorite goal-based quotas tuning
algorithm by writing special keywords to the file.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/dam... | null | null | null | [RFC PATCH 3/5] mm/damon/sysfs-schemes: implement quotas->goal_tuner file | Introduce a new goal-based DAMOS quota auto-tuning algorithm, namely
DAMOS_QUOTA_GOAL_TUNER_TEMPORAL (temporal in short). The algorithm aims
to trigger the DAMOS action only for a temporal time, until the goal is
achieved. For the temporal period, it uses as much quota as allowed.
Once the goal is achieved, it sets t... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Wed, 11 Feb 2026 22:23:09 -0800",
"is_openbsd": false,
"thread_id": "20260227015613.91346-1-sj@kernel.org.mbox.gz"
} |
lkml_critique | linux-mm | Add a new DAMON sysfs interface file, namely goal_tuner under the DAMOS
quotas directory. It is connected to the damos_quota->goal_tuner field.
Users can therefore select their favorite goal-based quotas tuning
algorithm by writing special keywords to the file.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/dam... | null | null | null | [RFC PATCH 3/5] mm/damon/sysfs-schemes: implement quotas->goal_tuner file | Aim-oriented DAMOS quota atuo-tuning uses a single tuning algorithm.
The algorithm is designed to find a non-zero quota that should be
consistently kept for achieving the aimed goal for long term. In other
words, the algorithm assumes the goal will be under-achieved once the
DAMOS scheme is completely deactivated. Me... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Wed, 11 Feb 2026 22:23:07 -0800",
"is_openbsd": false,
"thread_id": "20260227015613.91346-1-sj@kernel.org.mbox.gz"
} |
lkml_critique | linux-mm | Add a new DAMON sysfs interface file, namely goal_tuner under the DAMOS
quotas directory. It is connected to the damos_quota->goal_tuner field.
Users can therefore select their favorite goal-based quotas tuning
algorithm by writing special keywords to the file.
Signed-off-by: SeongJae Park <sj@kernel.org>
---
mm/dam... | null | null | null | [RFC PATCH 3/5] mm/damon/sysfs-schemes: implement quotas->goal_tuner file | On Wed, 11 Feb 2026 22:23:08 -0800 SeongJae Park <sj@kernel.org> wrote:
Ravi found this is resetting tuner setup in damon_sysfs_add_quota_score() in
sysfs-schemes.c. As a result, users were unable to use goal_tuner feature.
Ravi further suggested a fix that sets the goal_tuner after damon_new_scheme(),
as suggested ... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 17:56:13 -0800",
"is_openbsd": false,
"thread_id": "20260227015613.91346-1-sj@kernel.org.mbox.gz"
} |
lkml_critique | linux-mm | From: Qi Zheng <zhengqi.arch@bytedance.com>
Changes in v5:
- fix build error in [PATCH v4 24/31] (reported by kernel test robot)
- move the declaration of reparent_memcg_state_local() and
reparent_memcg_lruvec_state_local() into mm/memcontrol-v1.h file.
(suggested by Shakeel Butt, and due to some function depe... | null | null | null | [PATCH v5 00/32] Eliminate Dying Memory Cgroup | From: Muchun Song <songmuchun@bytedance.com>
Since the no-hierarchy mode has been deprecated after the commit:
commit bef8620cd8e0 ("mm: memcg: deprecate the non-hierarchical mode").
As a result, parent_mem_cgroup() will not return NULL except when passing
the root memcg, and the root memcg cannot be offline. Henc... | {
"author": "Qi Zheng <qi.zheng@linux.dev>",
"date": "Wed, 25 Feb 2026 15:48:34 +0800",
"is_openbsd": false,
"thread_id": "e15c2304-4874-4adc-bbe5-58ba78b3b84f@linux.dev.mbox.gz"
} |
lkml_critique | linux-mm | From: Qi Zheng <zhengqi.arch@bytedance.com>
Changes in v5:
- fix build error in [PATCH v4 24/31] (reported by kernel test robot)
- move the declaration of reparent_memcg_state_local() and
reparent_memcg_lruvec_state_local() into mm/memcontrol-v1.h file.
(suggested by Shakeel Butt, and due to some function depe... | null | null | null | [PATCH v5 00/32] Eliminate Dying Memory Cgroup | From: Muchun Song <songmuchun@bytedance.com>
Use folio_lruvec() to simplify the code.
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Qi Zheng <zhengqi.arch@bytedance.com>
Reviewed-by: Harry Yoo <harry.yoo@oracle.com>
Acked-by: Shakeel Butt <shakeel.... | {
"author": "Qi Zheng <qi.zheng@linux.dev>",
"date": "Wed, 25 Feb 2026 15:48:35 +0800",
"is_openbsd": false,
"thread_id": "e15c2304-4874-4adc-bbe5-58ba78b3b84f@linux.dev.mbox.gz"
} |
lkml_critique | linux-mm | From: Qi Zheng <zhengqi.arch@bytedance.com>
Changes in v5:
- fix build error in [PATCH v4 24/31] (reported by kernel test robot)
- move the declaration of reparent_memcg_state_local() and
reparent_memcg_lruvec_state_local() into mm/memcontrol-v1.h file.
(suggested by Shakeel Butt, and due to some function depe... | null | null | null | [PATCH v5 00/32] Eliminate Dying Memory Cgroup | From: Muchun Song <songmuchun@bytedance.com>
It is inappropriate to use folio_lruvec_lock() variants in conjunction
with unlock_page_lruvec() variants, as this involves the inconsistent
operation of locking a folio while unlocking a page. To rectify this, the
functions unlock_page_lruvec{_irq, _irqrestore} are renamed... | {
"author": "Qi Zheng <qi.zheng@linux.dev>",
"date": "Wed, 25 Feb 2026 15:48:36 +0800",
"is_openbsd": false,
"thread_id": "e15c2304-4874-4adc-bbe5-58ba78b3b84f@linux.dev.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.