All of lore.kernel.org
 help / color / mirror / Atom feed
* [folded-merged] mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas-fix.patch removed from -mm tree
@ 2025-03-17  4:44 Andrew Morton
  0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2025-03-17  4:44 UTC (permalink / raw)
  To: mm-commits, tglx, senozhatsky, peterz, nphamcs, minchan, herbert,
	hannes, chengming.zhou, yosry.ahmed, akpm


The quilt patch titled
     Subject: mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas-fix
has been removed from the -mm tree.  Its filename was
     mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas-fix.patch

This patch was dropped because it was folded into mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas.patch

------------------------------------------------------
From: Yosry Ahmed <yosry.ahmed@linux.dev>
Subject: mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas-fix
Date: Wed, 5 Mar 2025 18:57:51 +0000

update the docs

Link: https://lkml.kernel.org/r/Z8ier-ZZp8T6MOTH@google.com
Signed-off-by: Yosry Ahmed <yosry.ahmed@linux.dev>
Cc: Chengming Zhou <chengming.zhou@linux.dev>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Nhat Pham <nphamcs@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/mm/zsmalloc.rst |    5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

--- a/Documentation/mm/zsmalloc.rst~mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas-fix
+++ a/Documentation/mm/zsmalloc.rst
@@ -27,9 +27,8 @@ Instead, it returns an opaque handle (un
 location of the allocated object. The reason for this indirection is that
 zsmalloc does not keep zspages permanently mapped since that would cause
 issues on 32-bit systems where the VA region for kernel space mappings
-is very small. So, before using the allocating memory, the object has to
-be mapped using zs_map_object() to get a usable pointer and subsequently
-unmapped using zs_unmap_object().
+is very small. So, using the allocated memory should be done through the
+proper handle-based APIs.
 
 stat
 ====
_

Patches currently in -mm which might be from yosry.ahmed@linux.dev are

mm-z3fold-remove-z3fold.patch
mm-zbud-remove-zbud.patch
mm-zpool-add-interfaces-for-object-read-write-apis.patch
mm-zswap-use-object-read-write-apis-instead-of-object-mapping-apis.patch
mm-zpool-remove-object-mapping-apis.patch
mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas.patch
mm-zpool-remove-zpool_malloc_support_movable.patch


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-03-17  4:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-03-17  4:44 [folded-merged] mm-zsmalloc-remove-object-mapping-apis-and-per-cpu-map-areas-fix.patch removed from -mm tree Andrew Morton

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.