All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
	 Matthew Wilcox <willy@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, maple-tree@lists.infradead.org,
	 Christian Brauner <brauner@kernel.org>
Subject: [PATCH RFC v2 0/2] pidfs: use maple tree
Date: Mon, 09 Dec 2024 14:46:56 +0100	[thread overview]
Message-ID: <20241209-work-pidfs-maple_tree-v2-0-003dbf3bd96b@kernel.org> (raw)

Hey,

Ok, I wanted to give this another try as I'd really like to rely on the
maple tree supporting ULONG_MAX when BITS_PER_LONG is 64 as it makes
things a lot simpler overall.

As Willy didn't want additional users relying on an external lock I made
it so that we don't have to and can just use the mtree lock.

However, I need an irq safe variant which is why I added support for
this into the maple tree.

This is pullable from
https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git work.pidfs.maple_tree

Thanks!
Christian

---
Christian Brauner (2):
      maple_tree: make MT_FLAGS_LOCK_IRQ do something
      pidfs: use maple tree

 fs/pidfs.c                 | 52 +++++++++++++++++++++++++++-------------------
 include/linux/maple_tree.h | 16 ++++++++++++--
 kernel/pid.c               | 34 +++++++++++++++---------------
 3 files changed, 62 insertions(+), 40 deletions(-)
---
base-commit: 963c8e506c6d4769d04fcb64d4bf783e4ef6093e
change-id: 20241206-work-pidfs-maple_tree-b322ff5399b7


             reply	other threads:[~2024-12-09 13:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 13:46 Christian Brauner [this message]
2024-12-09 13:46 ` [PATCH RFC v2 1/2] maple_tree: make MT_FLAGS_LOCK_IRQ do something Christian Brauner
2024-12-09 13:46 ` [PATCH RFC v2 2/2] pidfs: use maple tree Christian Brauner
2024-12-13 10:35   ` Marek Szyprowski
2024-12-13 13:07     ` Christian Brauner
2024-12-13 14:16       ` Marek Szyprowski
2024-12-13 14:40 ` [PATCH RFC v2 0/2] " Liam R. Howlett
2024-12-13 18:51   ` Christian Brauner
2024-12-13 18:53     ` Matthew Wilcox
2024-12-13 19:01       ` Christian Brauner
2024-12-13 19:25         ` Christian Brauner
2024-12-13 20:11           ` Christian Brauner
2024-12-13 20:50             ` Christian Brauner
2024-12-13 21:07               ` Christian Brauner
2024-12-13 21:16                 ` Liam R. Howlett
2024-12-13 21:13               ` Liam R. Howlett
2024-12-13 21:04             ` Liam R. Howlett
2024-12-14 11:48               ` Christian Brauner
2024-12-17 17:41                 ` Liam R. Howlett

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=20241209-work-pidfs-maple_tree-v2-0-003dbf3bd96b@kernel.org \
    --to=brauner@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=maple-tree@lists.infradead.org \
    --cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.