From: "Ludovic Courtès" <ludo@gnu.org>
To: Tomas Volf <~@wolfsden.cz>
Cc: 68504@debbugs.gnu.org
Subject: bug#68504: [PATCH v3] Add copy-on-write support to scm_copy_file.
Date: Thu, 21 Mar 2024 15:23:33 +0100 [thread overview]
Message-ID: <87a5mrvf2y.fsf@gnu.org> (raw)
In-Reply-To: <ZfDi_NzJ9rFxJ3xN@ws> (Tomas Volf's message of "Wed, 13 Mar 2024 00:19:24 +0100")
Hi,
Tomas Volf <~@wolfsden.cz> skribis:
> Sure, I am willing to do my part. I managed to find this blog post[0], so after
> some minor troubles I did manage to get a VM with GNU/Hurd running. Next I will
> read up on copy_file_range and try to put together a patch.
It’s really just (service hurd-vm-service-type) on Guix System:
https://guix.gnu.org/manual/devel/en/html_node/Virtualization-Services.html#The-Hurd-in-a-Virtual-Machine
> Just to make sure, your idea here is exactly what? Always try to use
> copy_file_range before the regular copy? So the flow would be
>
> For 'always case:
>
> CoW ---fail--> FAIL
>
> For 'auto case:
>
> CoW ---fail--> copy_file_range ---fail--> current copy ---fail--> FAIL
>
> For 'never case:
>
> copy_file_range ---fail--> current copy ---fail--> FAIL
>
> Is that an accurate summary?
Yes, that’s exactly what I had in mind.
Actually it might be better to use sendfile(2), which is slightly less
generic but otherwise equivalent AFAICS, and which happens to have a
Hurd implementation in glibc.
Thanks for your help!
Ludo’.
prev parent reply other threads:[~2024-03-21 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 12:48 bug#68504: [PATCH] Add copy-on-write support to scm_copy_file Tomas Volf
2024-01-24 10:26 ` Ludovic Courtès
2024-01-24 19:19 ` Tomas Volf
2024-01-24 19:10 ` bug#68504: [PATCH v2] " Tomas Volf
2024-01-24 19:14 ` bug#68504: [PATCH v3] " Tomas Volf
2024-03-12 13:06 ` Ludovic Courtès
2024-03-12 23:19 ` Tomas Volf
2024-03-21 14:23 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5mrvf2y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=68504@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).