9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] Questions/concerns on gefs
Date: Mon, 26 Aug 2024 17:56:48 +0930	[thread overview]
Message-ID: <5FC659BC9D35777BAADAC92FAE79011C@musolino.id.au> (raw)
In-Reply-To: <be059bcf-e329-43c5-bce8-9e457a9d7814@fjrhome.net>

> One way to handle that would be to extend 9p to include a duplicate 
> command of some sort.  Then the utility would simply note that the file 
> is being copied to the same file server it is already located on and ask 
> that file server to duplicate it.  If the file server does not support 
> the command it reports an error back and cp falls back on its existing 
> behavior.

And then you have to extend the system call table so that cp and other
programs can acually do this kind of thing.  Not going to happen, I
don't think.

In any case, I don't think James was suggesting that cp would actually
have to be modified but rather that, like Hammer2, a filesystem could
deduplicate incoming writes (from cp(1) or wherever) against any data
it had already loaded off the disk(s).

--
Cheers,
Alex Musolino


  reply	other threads:[~2024-08-26  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  9:04 Timothy Robert Bednarzyk
2024-08-15  9:21 ` Steve Simon
2024-08-15  9:42 ` Stuart Morrow
2024-08-15 14:22 ` ori
2024-08-15 14:47   ` ori
2024-08-26  4:45   ` James Cook
2024-08-26  7:43     ` Steve Simon
2024-08-26  8:10       ` Frank D. Engel, Jr.
2024-08-26  8:26         ` Alex Musolino [this message]
2024-08-26 14:36         ` ron minnich

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=5FC659BC9D35777BAADAC92FAE79011C@musolino.id.au \
    --to=alex@musolino.id.au \
    --cc=9front@9front.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).