From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
Minchan Kim <minchan@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Nhat Pham <nphamcs@gmail.com>, Uros Bizjak <ubizjak@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/7] zsmalloc: preemptible object mapping
Date: Thu, 30 Jan 2025 23:21:16 +0900 [thread overview]
Message-ID: <x3b5fm2oecr5rlaytfpopbntg5mam2xsd6nnvvsgou2qxzegon@nsqfbkmhvnd7> (raw)
In-Reply-To: <20250130044455.2642465-1-senozhatsky@chromium.org>
On (25/01/30 13:42), Sergey Senozhatsky wrote:
> This is Part II of the series [1] that makes zram read() and write()
> preemptible. This part focuses only zsmalloc because zsmalloc imposes
> atomicity restrictions on its users. One notable example is object
> mapping API, which returns with:
> a) local CPU lock held
> b) zspage rwlock held
I'll combine this series and zram series [1] and send out as one patch
set.
[1] https://lore.kernel.org/linux-mm/20250130111105.2861324-1-senozhatsky@chromium.org
prev parent reply other threads:[~2025-01-30 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 4:42 Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 1/7] zsmalloc: factor out pool locking helpers Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 2/7] zsmalloc: re-shuffle zs_pool members Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 3/7] zsmalloc: factor out size-class locking helpers Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 4/7] zsmalloc: make zspage lock preemptible Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 5/7] zsmalloc: introduce new object mapping API Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 6/7] zram: switch to new zsmalloc " Sergey Senozhatsky
2025-01-30 4:42 ` [PATCHv2 7/7] zram: add might_sleep to zcomp API Sergey Senozhatsky
2025-01-30 14:21 ` Sergey Senozhatsky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x3b5fm2oecr5rlaytfpopbntg5mam2xsd6nnvvsgou2qxzegon@nsqfbkmhvnd7 \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=ubizjak@gmail.com \
--cc=yosry.ahmed@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox