public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
	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 v3 0/3] zram: Replace bit spinlocks with a spinlock_t.
Date: Thu, 8 Aug 2024 11:03:18 +0200	[thread overview]
Message-ID: <20240808090318.OYWITKyu@linutronix.de> (raw)
In-Reply-To: <20240705125058.1564001-1-bigeasy@linutronix.de>

On 2024-07-05 14:49:13 [+0200], To linux-block@vger.kernel.org wrote:
Hi,

> 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.
> 
> v2…v3 https://lore.kernel.org/all/20240620153556.777272-1-bigeasy@linutronix.de/
>   - Do "size_t index" within the for loop.

Can this be applied, please? Or v2 ;)

Sebastian

      parent reply	other threads:[~2024-08-08  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 12:49 [PATCH v3 0/3] zram: Replace bit spinlocks with a spinlock_t Sebastian Andrzej Siewior
2024-07-05 12:49 ` [PATCH v3 1/3] " Sebastian Andrzej Siewior
2024-07-05 12:49 ` [PATCH v3 2/3] zram: Remove ZRAM_LOCK Sebastian Andrzej Siewior
2024-07-05 12:49 ` [PATCH v3 3/3] zram: Shrink zram_table_entry::flags Sebastian Andrzej Siewior
2024-08-08  9:03 ` Sebastian Andrzej Siewior [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=20240808090318.OYWITKyu@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=aleksander.lobakin@intel.com \
    --cc=axboe@kernel.dk \
    --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