linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Liam Howlett <liam.howlett@oracle.com>,
	kernel test robot <oliver.sang@intel.com>,
	Feng Tang <feng.tang@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"maple-tree@lists.infradead.org" <maple-tree@lists.infradead.org>,
	linux-mm <linux-mm@kvack.org>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH RFC 0/7] Use Maple Trees for simple_offset utilities
Date: Tue, 13 Feb 2024 21:40:35 +0000	[thread overview]
Message-ID: <61820F51-AB93-45D1-812C-D6EAA089AE3E@oracle.com> (raw)
In-Reply-To: <170785993027.11135.8830043889278631735.stgit@91.116.238.104.host.secureserver.net>



> On Feb 13, 2024, at 4:37 PM, Chuck Lever <cel@kernel.org> wrote:
> 
> In an effort to address slab fragmentation issues reported a few
> months ago, I've replaced the use of xarrays for the directory
> offset map in "simple" file systems (including tmpfs).
> 
> This patch set passes functional testing and is ready for code
> review. But I don't have the facilities to re-run the performance
> tests that identified the regression. We expect the performance of
> this implementation will need additional improvement.
> 
> Thanks to Liam Howlett for helping me get this working.

And note the patches are also available from:

https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git

in the simple-offset-maple branch.


> ---
> 
> Chuck Lever (6):
>      libfs: Rename "so_ctx"
>      libfs: Define a minimum directory offset
>      libfs: Add simple_offset_empty()
>      maple_tree: Add mtree_alloc_cyclic()
>      libfs: Convert simple directory offsets to use a Maple Tree
>      libfs: Re-arrange locking in offset_iterate_dir()
> 
> Liam R. Howlett (1):
>      test_maple_tree: testing the cyclic allocation
> 
> 
> fs/libfs.c                 | 125 +++++++++++++++++++++++--------------
> include/linux/fs.h         |   6 +-
> include/linux/maple_tree.h |   7 +++
> lib/maple_tree.c           |  93 +++++++++++++++++++++++++++
> lib/test_maple_tree.c      |  44 +++++++++++++
> mm/shmem.c                 |   4 +-
> 6 files changed, 227 insertions(+), 52 deletions(-)
> 
> --
> Chuck Lever
> 
> 

--
Chuck Lever



      parent reply	other threads:[~2024-02-13 21:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 21:37 Chuck Lever
2024-02-13 21:37 ` [PATCH RFC 1/7] libfs: Rename "so_ctx" Chuck Lever
2024-02-15 12:42   ` Jan Kara
2024-02-13 21:37 ` [PATCH RFC 2/7] libfs: Define a minimum directory offset Chuck Lever
2024-02-15 12:47   ` Jan Kara
2024-02-13 21:37 ` [PATCH RFC 3/7] libfs: Add simple_offset_empty() Chuck Lever
2024-02-15 12:53   ` Jan Kara
2024-02-13 21:37 ` [PATCH RFC 4/7] maple_tree: Add mtree_alloc_cyclic() Chuck Lever
2024-02-13 21:37 ` [PATCH RFC 5/7] test_maple_tree: testing the cyclic allocation Chuck Lever
2024-02-13 21:38 ` [PATCH RFC 6/7] libfs: Convert simple directory offsets to use a Maple Tree Chuck Lever
2024-02-15 13:06   ` Jan Kara
2024-02-15 13:45     ` Chuck Lever
2024-02-15 14:02       ` Jan Kara
2024-02-16 15:15       ` Christian Brauner
2024-02-18  2:02       ` Oliver Sang
2024-02-18 15:57         ` Chuck Lever
2024-02-19  6:00           ` Oliver Sang
2024-02-13 21:38 ` [PATCH RFC 7/7] libfs: Re-arrange locking in offset_iterate_dir() Chuck Lever
2024-02-15 13:16   ` Jan Kara
2024-02-15 17:00     ` Liam R. Howlett
2024-02-15 17:16       ` Jan Kara
2024-02-15 21:07         ` Liam R. Howlett
2024-02-16 10:15           ` Jan Kara
2024-02-16 15:57             ` Matthew Wilcox
2024-02-16 16:33             ` Liam R. Howlett
2024-02-19 18:06               ` Jan Kara
2024-02-15 17:40       ` Chuck Lever
2024-02-15 21:08         ` Liam R. Howlett
2024-02-13 21:40 ` Chuck Lever III [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=61820F51-AB93-45D1-812C-D6EAA089AE3E@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=feng.tang@intel.com \
    --cc=hughd@google.com \
    --cc=jack@suse.cz \
    --cc=liam.howlett@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=maple-tree@lists.infradead.org \
    --cc=oliver.sang@intel.com \
    --cc=viro@zeniv.linux.org.uk \
    /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