mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	Minchan Kim <minchan@kernel.org>,
	 Sergey Senozhatsky <senozhatsky@chromium.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 1/2] zram: Move lockmap to be per-zram instead per table
Date: Fri, 24 Jul 2026 12:25:13 +0900	[thread overview]
Message-ID: <amLa8bS723DLgKyd@google.com> (raw)
In-Reply-To: <20260714141300.3945672-2-bigeasy@linutronix.de>

On (26/07/14 16:12), Sebastian Andrzej Siewior wrote:
> The zram object contains an array zram_table_entry. Each one has a
> `lock' variable and each has a matching struct lockdep_map. This mimics
> a struct mutex.
> 
> It uses always the same key for all lockdep_map instances. This makes it
> look like the same lock to lockdep. Therefore it could be reduced to
> have one lockdep_map per struct zram.
> 
> Use only one struct lockdep_map per struct zram.
> 
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>

Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Tested-by: Sergey Senozhatsky <senozhatsky@chromium.org>

  reply	other threads:[~2026-07-24  3:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 14:12 [PATCH 0/2] zram: lockmap tweaks Sebastian Andrzej Siewior
2026-07-14 14:12 ` [PATCH 1/2] zram: Move lockmap to be per-zram instead per table Sebastian Andrzej Siewior
2026-07-24  3:25   ` Sergey Senozhatsky [this message]
2026-07-14 14:13 ` [PATCH 2/2] zram: Use a custom key for each zram object Sebastian Andrzej Siewior
2026-07-24  3:24   ` Sergey Senozhatsky
2026-07-24  7:52     ` Sergey Senozhatsky
2026-07-24  3:26 ` [PATCH 0/2] zram: lockmap tweaks Sergey Senozhatsky
2026-07-24  3:31 ` Sergey Senozhatsky

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=amLa8bS723DLgKyd@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=bigeasy@linutronix.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    /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
Powered by JetHome