From: "Darrick J. Wong" <djwong@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [GIT PULL v2] xfs: buffer cache bulk page allocation
Date: Wed, 9 Jun 2021 13:46:45 -0700 [thread overview]
Message-ID: <20210609204645.GY2945738@locust> (raw)
In-Reply-To: <20210608041437.GA2419729@dread.disaster.area>
On Tue, Jun 08, 2021 at 02:14:37PM +1000, Dave Chinner wrote:
> Hi Darrick,
>
> As we talked about on IRC, I have (force) updated the branch and tag
> containing the buffer cache bulk page allocation series to correct
> the errors in the commit metadata. This version correctly attributes
> all of Christoph's patches, fixes a couple of minor typos and adds a
> missing committer SoB to another of Christoph's patches. There are
> no code changes in this update.
>
> When you next update the for-next branch, can you please pull the
> updates from the tag below?
Pulled, thanks.
--D
>
> Cheers,
>
> Dave.
>
> The following changes since commit d07f6ca923ea0927a1024dfccafc5b53b61cfecc:
>
> Linux 5.13-rc2 (2021-05-16 15:27:44 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git tags/xfs-buf-bulk-alloc-tag
>
> for you to fetch changes up to 8bcac7448a942fa4662441a310c97d47cec24310:
>
> xfs: merge xfs_buf_allocate_memory (2021-06-07 11:50:48 +1000)
>
> ----------------------------------------------------------------
> xfs: buffer cache bulk page allocation
>
> This patchset makes use of the new bulk page allocation interface to
> reduce the overhead of allocating large numbers of pages in a
> loop.
>
> The first two patches are refactoring buffer memory allocation and
> converting the uncached buffer path to use the same page allocation
> path, followed by converting the page allocation path to use bulk
> allocation.
>
> The rest of the patches are then consolidation of the page
> allocation and freeing code to simplify the code and remove a chunk
> of unnecessary abstraction. This is largely based on a series of
> changes made by Christoph Hellwig.
>
> ----------------------------------------------------------------
> Christoph Hellwig (3):
> xfs: remove ->b_offset handling for page backed buffers
> xfs: simplify the b_page_count calculation
> xfs: cleanup error handling in xfs_buf_get_map
>
> Dave Chinner (7):
> xfs: split up xfs_buf_allocate_memory
> xfs: use xfs_buf_alloc_pages for uncached buffers
> xfs: use alloc_pages_bulk_array() for buffers
> xfs: merge _xfs_buf_get_pages()
> xfs: move page freeing into _xfs_buf_free_pages()
> xfs: get rid of xb_to_gfp()
> xfs: merge xfs_buf_allocate_memory
>
> fs/xfs/libxfs/xfs_ag.c | 1 -
> fs/xfs/xfs_buf.c | 305 ++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------
> fs/xfs/xfs_buf.h | 3 +-
> 3 files changed, 120 insertions(+), 189 deletions(-)
>
> --
> Dave Chinner
> david@fromorbit.com
prev parent reply other threads:[~2021-06-09 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210608035616.GJ664593@dread.disaster.area>
2021-06-08 4:14 ` [GIT PULL v2] xfs: buffer cache bulk page allocation Dave Chinner
2021-06-09 20:46 ` Darrick J. Wong [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=20210609204645.GY2945738@locust \
--to=djwong@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.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