public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Will Deacon <will@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] locking changes for v5.8
Date: Mon, 1 Jun 2020 15:32:28 +0200	[thread overview]
Message-ID: <20200601133228.GA834929@gmail.com> (raw)

Linus,

Please pull the latest locking/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2020-06-01

   # HEAD: 19f545b6e07f753c4dc639c2f0ab52345733b6a8 zram: Use local lock to protect per-CPU data

The biggest change to core locking facilities in this cycle is the introduction
of local_lock_t - this primitive comes from the -rt project and identifies
CPU-local locking dependencies normally handled opaquely beind preempt_disable()
or local_irq_save/disable() critical sections.

The generated code on mainline kernels doesn't change as a result, but still there
are benefits: improved debugging and better documentation of data structure
accesses.

The new local_lock_t primitives are introduced and then utilized in a couple of
kernel subsystems. No change in functionality is intended.

There's also other smaller changes and cleanups.

 Thanks,

	Ingo

------------------>
Alex Shi (1):
      locking/rtmutex: Remove unused rt_mutex_cmpxchg_relaxed()

Gustavo A. R. Silva (1):
      locking/lockdep: Replace zero-length array with flexible-array

Ingo Molnar (1):
      mm/swap: Use local_lock for protection

Julia Cartwright (1):
      squashfs: Make use of local lock in multi_cpu decompressor

Mike Galbraith (2):
      connector/cn_proc: Protect send_msg() with a local lock
      zram: Use local lock to protect per-CPU data

Sebastian Andrzej Siewior (2):
      radix-tree: Use local_lock for protection
      zram: Allocate struct zcomp_strm as per-CPU memory

Thomas Gleixner (1):
      locking: Introduce local_lock()


 Documentation/locking/locktypes.rst     | 215 ++++++++++++++++++++++++++++++--
 drivers/block/zram/zcomp.c              |  44 +++----
 drivers/block/zram/zcomp.h              |   5 +-
 drivers/connector/cn_proc.c             |  21 ++--
 fs/squashfs/decompressor_multi_percpu.c |  21 ++--
 include/linux/idr.h                     |   2 +-
 include/linux/local_lock.h              |  54 ++++++++
 include/linux/local_lock_internal.h     |  90 +++++++++++++
 include/linux/radix-tree.h              |  11 +-
 include/linux/swap.h                    |   1 +
 kernel/locking/lockdep.c                |   2 +-
 kernel/locking/rtmutex.c                |   2 -
 lib/radix-tree.c                        |  20 ++-
 mm/compaction.c                         |   6 +-
 mm/swap.c                               | 118 ++++++++++++------
 15 files changed, 502 insertions(+), 110 deletions(-)
 create mode 100644 include/linux/local_lock.h
 create mode 100644 include/linux/local_lock_internal.h

             reply	other threads:[~2020-06-01 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 13:32 Ingo Molnar [this message]
2020-06-01 21:55 ` [GIT PULL] locking changes for v5.8 pr-tracker-bot

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=20200601133228.GA834929@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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