public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git namespace stuff
Date: Fri, 24 Feb 2023 03:35:16 +0000	[thread overview]
Message-ID: <Y/gwdJrHLvEC1lCn@ZenIV> (raw)

	Rik's patches reducing the amount of synchronize_rcu() triggered
by ipc namespace destruction.  I've some pending stuff reducing that on
the normal umount side, but it's nowhere near ready and Rik's stuff shouldn't
be held back due to conflicts - I'll just redo the parts of my series that
stray into ipc/*.

The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:

  Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.namespace

for you to fetch changes up to da27f796a832122ee533c7685438dad1c4e338dd:

  ipc,namespace: batch free ipc_namespace structures (2023-01-27 19:08:00 -0500)

----------------------------------------------------------------
Rik van Riel (2):
      ipc,namespace: make ipc namespace allocation wait for pending free
      ipc,namespace: batch free ipc_namespace structures

 fs/namespace.c        | 18 ++++++++++++++----
 include/linux/mount.h |  1 +
 ipc/mqueue.c          |  5 -----
 ipc/namespace.c       | 35 ++++++++++++++++++++++++++---------
 ipc/util.h            |  2 --
 5 files changed, 41 insertions(+), 20 deletions(-)

             reply	other threads:[~2023-02-24  3:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  3:35 Al Viro [this message]
2023-02-25  3:40 ` [git pull] vfs.git namespace stuff 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=Y/gwdJrHLvEC1lCn@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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