From: Jens Axboe <axboe@kernel.dk>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mike Galbraith <umgwanakikbuti@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: Re: [PATCH v4 0/3] zram: Replace bit spinlocks with a spinlock_t.
Date: Fri, 06 Sep 2024 08:51:21 -0600 [thread overview]
Message-ID: <172563428176.173362.6692138069455842459.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240906141520.730009-1-bigeasy@linutronix.de>
On Fri, 06 Sep 2024 16:14:42 +0200, Sebastian Andrzej Siewior wrote:
> this is follow up to the previous posting, making the lock
> unconditionally. The original problem with bit spinlock is that it
> disabled preemption and the following operations (within the atomic
> section) perform operations that may sleep on PREEMPT_RT. Mike expressed
> that he would like to keep using zram on PREEMPT_RT.
>
> v3…v4: https://lore.kernel.org/linux-block/20240705125058.1564001-1-bigeasy@linutronix.de
> - Inline lock init into zram_meta_alloc().
>
> [...]
Applied, thanks!
[1/3] zram: Replace bit spinlocks with a spinlock_t.
commit: 9518e5bfaae19447d657983d0628062ab6712610
[2/3] zram: Remove ZRAM_LOCK
commit: 6086aeb49e3d9e25165769b2a0a13ff67f98a1a2
[3/3] zram: Shrink zram_table_entry::flags.
commit: 68d20eb60efbdc80662efedeb088353e9c4aa17f
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-09-06 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 14:14 Sebastian Andrzej Siewior
2024-09-06 14:14 ` [PATCH v4 1/3] " Sebastian Andrzej Siewior
2024-09-06 14:14 ` [PATCH v4 2/3] zram: Remove ZRAM_LOCK Sebastian Andrzej Siewior
2024-09-06 14:14 ` [PATCH v4 3/3] zram: Shrink zram_table_entry::flags Sebastian Andrzej Siewior
2024-09-06 14:31 ` [PATCH v4 0/3] zram: Replace bit spinlocks with a spinlock_t Jens Axboe
2024-09-06 14:48 ` Sebastian Andrzej Siewior
2024-09-06 14:50 ` Jens Axboe
2024-09-06 14:51 ` Jens Axboe [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=172563428176.173362.6692138069455842459.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=aleksander.lobakin@intel.com \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®