From: Chandan Babu R <chandanrlinux@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: reduce buffer log item shadow allocations
Date: Tue, 02 Feb 2021 17:31:37 +0530 [thread overview]
Message-ID: <87im7an0f2.fsf@garuda> (raw)
In-Reply-To: <20210128044154.806715-6-david@fromorbit.com>
On 28 Jan 2021 at 10:11, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> When we modify btrees repeatedly, we regularly increase the size of
> the logged region by a single chunk at a time (per transaction
> commit). This results in the CIL formatting code having to
> reallocate the log vector buffer every time the buffer dirty region
> grows. Hence over a typical 4kB btree buffer, we might grow the log
> vector 4096/128 = 32x over a short period where we repeatedly add
> or remove records to/from the buffer over a series of running
> transaction. This means we are doing 32 memory allocations and frees
> over this time during a performance critical path in the journal.
>
> The amount of space tracked in the CIL for the object is calculated
> during the ->iop_format() call for the buffer log item, but the
> buffer memory allocated for it is calculated by the ->iop_size()
> call. The size callout determines the size of the buffer, the format
> call determines the space used in the buffer.
>
> Hence we can oversize the buffer space required in the size
> calculation without impacting the amount of space used and accounted
> to the CIL for the changes being logged. This allows us to reduce
> the number of allocations by rounding up the buffer size to allow
> for future growth. This can safe a substantial amount of CPU time in
> this path:
>
> - 46.52% 2.02% [kernel] [k] xfs_log_commit_cil
> - 44.49% xfs_log_commit_cil
> - 30.78% _raw_spin_lock
> - 30.75% do_raw_spin_lock
> 30.27% __pv_queued_spin_lock_slowpath
>
> (oh, ouch!)
> ....
> - 1.05% kmem_alloc_large
> - 1.02% kmem_alloc
> 0.94% __kmalloc
>
> This overhead here us what this patch is aimed at. After:
>
> - 0.76% kmem_alloc_large ▒
> - 0.75% kmem_alloc ▒
> 0.70% __kmalloc ▒
Apart from the trailing whitespace above,
The changes look good to me.
Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> fs/xfs/xfs_buf_item.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_buf_item.c b/fs/xfs/xfs_buf_item.c
> index 17960b1ce5ef..0628a65d9c55 100644
> --- a/fs/xfs/xfs_buf_item.c
> +++ b/fs/xfs/xfs_buf_item.c
> @@ -142,6 +142,7 @@ xfs_buf_item_size(
> {
> struct xfs_buf_log_item *bip = BUF_ITEM(lip);
> int i;
> + int bytes;
>
> ASSERT(atomic_read(&bip->bli_refcount) > 0);
> if (bip->bli_flags & XFS_BLI_STALE) {
> @@ -173,7 +174,7 @@ xfs_buf_item_size(
> }
>
> /*
> - * the vector count is based on the number of buffer vectors we have
> + * The vector count is based on the number of buffer vectors we have
> * dirty bits in. This will only be greater than one when we have a
> * compound buffer with more than one segment dirty. Hence for compound
> * buffers we need to track which segment the dirty bits correspond to,
> @@ -181,10 +182,18 @@ xfs_buf_item_size(
> * count for the extra buf log format structure that will need to be
> * written.
> */
> + bytes = 0;
> for (i = 0; i < bip->bli_format_count; i++) {
> xfs_buf_item_size_segment(bip, &bip->bli_formats[i],
> - nvecs, nbytes);
> + nvecs, &bytes);
> }
> +
> + /*
> + * Round up the buffer size required to minimise the number of memory
> + * allocations that need to be done as this item grows when relogged by
> + * repeated modifications.
> + */
> + *nbytes = round_up(bytes, 512);
> trace_xfs_buf_item_size(bip);
> }
--
chandan
next prev parent reply other threads:[~2021-02-02 12:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 4:41 [PATCH 0/5] xfs: various log stuff Dave Chinner
2021-01-28 4:41 ` [PATCH 1/5] xfs: log stripe roundoff is a property of the log Dave Chinner
2021-01-28 14:57 ` Brian Foster
2021-01-28 20:59 ` Dave Chinner
2021-01-28 21:25 ` Darrick J. Wong
2021-01-28 22:00 ` Dave Chinner
2021-01-28 4:41 ` [PATCH 2/5] xfs: separate CIL commit record IO Dave Chinner
2021-01-28 15:07 ` Brian Foster
2021-01-28 21:22 ` Dave Chinner
[not found] ` <20210129145851.GB2660974@bfoster>
2021-01-29 22:25 ` Dave Chinner
2021-02-01 16:07 ` Brian Foster
2021-01-30 9:13 ` Chandan Babu R
2021-02-01 12:59 ` Christoph Hellwig
2021-01-28 4:41 ` [PATCH 3/5] xfs: journal IO cache flush reductions Dave Chinner
2021-01-28 15:12 ` Brian Foster
2021-01-28 21:46 ` Dave Chinner
2021-01-28 21:26 ` Dave Chinner
2021-01-30 12:56 ` Chandan Babu R
2021-01-28 4:41 ` [PATCH 4/5] xfs: Fix CIL throttle hang when CIL space used going backwards Dave Chinner
2021-01-28 16:53 ` Brian Foster
2021-02-02 5:52 ` Chandan Babu R
2021-02-17 11:33 ` Paul Menzel
2021-02-17 21:06 ` Donald Buczek
2021-01-28 4:41 ` [PATCH 5/5] xfs: reduce buffer log item shadow allocations Dave Chinner
2021-01-28 16:54 ` Brian Foster
2021-01-28 21:58 ` Dave Chinner
2021-02-02 12:01 ` Chandan Babu R [this message]
2021-02-01 12:39 ` [PATCH 0/5] xfs: various log stuff Christoph Hellwig
2021-02-03 21:20 ` Dave Chinner
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=87im7an0f2.fsf@garuda \
--to=chandanrlinux@gmail.com \
--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