From: Nicolas Schier <nsc@kernel.org>
To: David Disseldorp <ddiss@suse.de>
Cc: linux-kbuild@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCH v2 0/7] gen_init_cpio: add copy_file_range / reflink support
Date: Mon, 18 Aug 2025 20:40:23 +0200 [thread overview]
Message-ID: <aKNzl1Oo2zzPYGQP@levanger> (raw)
In-Reply-To: <20250814054818.7266-1-ddiss@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Thu, Aug 14, 2025 at 03:17:58PM +1000, David Disseldorp wrote:
> This patchset adds copy_file_range() support to gen_init_cpio. When
> combined with data segment alignment, large-file archiving performance
> is improved on Btrfs and XFS due to reflinks (see 7/7 benchmarks).
>
> cpio data segment alignment is provided by "bending" the newc spec
> to zero-pad the filename field. GNU cpio and Linux initramfs extractors
> handle this fine as long as PATH_MAX isn't exceeded.
>
> Changes since v1 RFC
> - add alignment patches 6-7
> - slightly rework commit and error messages
> - rename l->len to avoid 1/i confusion
>
> David Disseldorp (7):
> gen_init_cpio: write to fd instead of stdout stream
> gen_init_cpio: support -o <output_path> parameter
> gen_init_cpio: attempt copy_file_range for file data
> gen_init_cpio: avoid duplicate strlen calls
> gen_initramfs.sh: use gen_init_cpio -o parameter
> docs: initramfs: file data alignment via name padding
> gen_init_cpio: add -a <data_align> as reflink optimization
>
> .../driver-api/early-userspace/buffer-format.rst | 5 +
> usr/gen_init_cpio.c | 234 ++++++++++++++-------
> usr/gen_initramfs.sh | 7 +-
> 3 files changed, 166 insertions(+), 80 deletions(-)
>
>
Thanks for the series! I have found only a minor nick pick and some few
bike-shedding things.
Reviewed-by: Nicolas Schier <nsc@kernel.org>
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-08-18 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 5:17 [PATCH v2 0/7] gen_init_cpio: add copy_file_range / reflink support David Disseldorp
2025-08-14 5:17 ` [PATCH v2 1/7] gen_init_cpio: write to fd instead of stdout stream David Disseldorp
2025-08-18 18:40 ` Nicolas Schier
2025-08-14 5:18 ` [PATCH v2 2/7] gen_init_cpio: support -o <output_path> parameter David Disseldorp
2025-08-18 18:40 ` Nicolas Schier
2025-08-14 5:18 ` [PATCH v2 3/7] gen_init_cpio: attempt copy_file_range for file data David Disseldorp
2025-08-18 18:40 ` Nicolas Schier
2025-08-19 0:20 ` David Disseldorp
2025-08-14 5:18 ` [PATCH v2 4/7] gen_init_cpio: avoid duplicate strlen calls David Disseldorp
2025-08-14 5:18 ` [PATCH v2 5/7] gen_initramfs.sh: use gen_init_cpio -o parameter David Disseldorp
2025-08-18 18:40 ` Nicolas Schier
2025-08-14 5:18 ` [PATCH v2 6/7] docs: initramfs: file data alignment via name padding David Disseldorp
2025-08-14 5:18 ` [PATCH v2 7/7] gen_init_cpio: add -a <data_align> as reflink optimization David Disseldorp
2025-08-18 19:23 ` Nicolas Schier
2025-08-21 8:10 ` David Disseldorp
2025-08-18 18:40 ` Nicolas Schier [this message]
2025-08-18 23:46 ` [PATCH v2 0/7] gen_init_cpio: add copy_file_range / reflink support David Disseldorp
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=aKNzl1Oo2zzPYGQP@levanger \
--to=nsc@kernel.org \
--cc=ddiss@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-next@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