From: alexjlzheng@gmail.com
To: chandan.babu@oracle.com, djwong@kernel.org
Cc: david@fromorbit.com, hch@infradead.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
alexjlzheng@tencent.com
Subject: [PATCH xfs v2 0/2] Separate xfs_log_vec/iovec to save memory
Date: Wed, 26 Jun 2024 02:28:40 +0800 [thread overview]
Message-ID: <20240625182842.1038809-1-alexjlzheng@tencent.com> (raw)
From: Jinliang Zheng <alexjlzheng@tencent.com>
xfs_log_iovec dominates the memory usage of the
xfs_log_vec/xfs_log_iovec combination, and it is no longer useful after
the data is flushed to the iclog. This patchset separates xfs_log_iovec
from xfs_log_vec and releases them early to save memory.
Changelog:
V1:
- https://lore.kernel.org/linux-xfs/20240623123119.3562031-1-alexjlzheng@tencent.com/
V2:
- add kmem_cache for small object xfs_log_vec
- reduce redundant free and allocation of xfs_log_vec
Jinliang Zheng (2):
xfs: add xfs_log_vec_cache for separate xfs_log_vec/xfs_log_iovec
xfs: make xfs_log_iovec independent from xfs_log_vec and free it early
fs/xfs/xfs_log.c | 3 +++
fs/xfs/xfs_log.h | 10 ++++++++--
fs/xfs/xfs_log_cil.c | 33 ++++++++++++++++++++-------------
fs/xfs/xfs_super.c | 9 +++++++++
4 files changed, 40 insertions(+), 15 deletions(-)
--
2.39.3
next reply other threads:[~2024-06-25 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 18:28 alexjlzheng [this message]
2024-06-25 18:28 ` [PATCH xfs v2 1/2] xfs: add xfs_log_vec_cache for separate xfs_log_vec/xfs_log_iovec alexjlzheng
2024-06-25 18:28 ` [PATCH xfs v2 2/2] xfs: make xfs_log_iovec independent from xfs_log_vec and free it early alexjlzheng
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=20240625182842.1038809-1-alexjlzheng@tencent.com \
--to=alexjlzheng@gmail.com \
--cc=alexjlzheng@tencent.com \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).