Date: Thu, 11 Feb 2021 19:00:46 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Ka Ho Ng <khng@freebsdfoundation.org>, Ka Ho Ng via freebsd-arch <freebsd-arch@freebsd.org> Subject: Re: Proposing space management API to perform hole-punching Message-ID: <82972.1613070046@critter.freebsd.dk> In-Reply-To: <17D576F5-FBB9-425A-B6AB-B6CBA97ED785@freebsdfoundation.org> References: <17D576F5-FBB9-425A-B6AB-B6CBA97ED785@freebsdfoundation.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- Ka Ho Ng via freebsd-arch writes: > The proposal contains fspacectl(2), VOP_DEALLOCATE(9) and vn_deallocate(= 9). fspacectl(2) is a space management API that takes a file descriptor, a= command value, a range and flags. The system call is responsible for doi= ng space management operations such as punching holes, which is the only o= peration supported so far. [...] 1. Which other operations are/can be foreseen ? 2. What arguments would they need ? 3. Should the syscall definition take this into account already now ? 4. Are there any existing APIs for this ? 5. Should we stick closely to them ? If not, why not ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82972.1613070046>