public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Sebastian Huber <sh@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Add FIOBMAP2 ioctl
Date: Mon, 11 Jul 2022 11:50:18 +0000 (GMT)	[thread overview]
Message-ID: <20220711115018.90AF5385414E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=8fe49db783fd0841296afaf0226f712bc5967f4b

commit 8fe49db783fd0841296afaf0226f712bc5967f4b
Author: Alan Somers <asomers@FreeBSD.org>
Date:   Thu Jun 20 14:13:10 2019 +0000

    Add FIOBMAP2 ioctl
    
    This ioctl exposes VOP_BMAP information to userland. It can be used by
    programs like fragmentation analyzers and optimized cp implementations. But
    I'm using it to test fusefs's VOP_BMAP implementation. The "2" in the name
    distinguishes it from the similar but incompatible FIBMAP ioctls in NetBSD
    and Linux.  FIOBMAP2 differs from FIBMAP in that it uses a 64-bit block
    number instead of 32-bit, and it also returns runp and runb.
    
    Reviewed by:    mckusick
    MFC after:      2 weeks
    Sponsored by:   The FreeBSD Foundation
    Differential Revision:  https://reviews.freebsd.org/D20705

Diff:
---
 newlib/libc/sys/rtems/include/sys/filio.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/newlib/libc/sys/rtems/include/sys/filio.h b/newlib/libc/sys/rtems/include/sys/filio.h
index 868fe53c2..1a3fc4293 100644
--- a/newlib/libc/sys/rtems/include/sys/filio.h
+++ b/newlib/libc/sys/rtems/include/sys/filio.h
@@ -62,6 +62,13 @@ struct fiodgname_arg {
 /* Handle lseek SEEK_DATA and SEEK_HOLE for holey file knowledge. */
 #define	FIOSEEKDATA	_IOWR('f', 97, off_t)	/* SEEK_DATA */
 #define	FIOSEEKHOLE	_IOWR('f', 98, off_t)	/* SEEK_HOLE */
+struct fiobmap2_arg {
+	int64_t	bn;
+	int	runp;
+	int	runb;
+};
+/* Get the file's bmap info for the logical block bn */
+#define FIOBMAP2	_IOWR('f', 99, struct fiobmap2_arg)
 
 #ifdef _KERNEL
 #ifdef COMPAT_FREEBSD32


                 reply	other threads:[~2022-07-11 11:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220711115018.90AF5385414E@sourceware.org \
    --to=sh@sourceware.org \
    --cc=newlib-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).