Skip to contentSkip to conversation

Recent changes (master)

PATCH Jens Axboe 1 participant 1 message Aug 19, 2025

lore
Share & tools
lore

Jens Axboe

author
#0 lore raw

The following changes since commit fef641096d925d737d81683626eca52b6e358e52:

configure: skip isal64 check when isal check fails (2025-08-11 12:42:06 -0400)

are available in the Git repository at:

git://git.kernel.dk/fio.git master

for you to fetch changes up to 7664dccc0b2e3de04a0fd6f0be63402716c5f6b7:

Merge branch 'http-range-header' of https://github.com/sfc-gh-rnarubin/fio (2025-08-18 13:53:46 -0400)

----------------------------------------------------------------
Renar Narubin (1):
engines/http: Add support for range reads

Vincent Fu (1):
Merge branch 'http-range-header' of https://github.com/sfc-gh-rnarubin/fio

 HOWTO.rst      | 18 +++++++++++++
 engines/http.c | 83 ++++++++++++++++++++++++++++++++++++++++++++++++----------
 fio.1          | 20 ++++++++++++++
 3 files changed, 107 insertions(+), 14 deletions(-)

---

Diff of recent changes:

HOWTO.rst +18 -0
index 55ebc388..3eb0d9fe 100644
@@ -3058,6 +3058,24 @@ with the caveat that when used on the command line, they must come after the
 	turns on verbose logging from libcurl, 2 additionally enables
 	HTTP IO tracing. Default is **0**
 
+.. option:: http_object_mode=str : [http]
+
+        How to structure objects for HTTP IO: *block* or *range*.
+        Default is **block**.
+
+        In *block* mode, one object is created for every block. The HTTP engine
+        treats :option:`blocksize` as the size of the object to read or write,
+        and appends the block start/end offsets to the :option:`filename` to
+        create the target object path. Reads and writes operate on whole
+        objects at a time.
+
+        In *range* mode, one object is created for every file. The object path
+        is the filename directly for both read and write I/O. For read
+        requests, the :option:`blocksize` and :option:`offset` will be used to
+        set the "Range" header on read requests to issue partial reads of the
+        object. For write requests, blocksize is used to set the size of the
+        object, the same as in *block* mode.
+
 .. option:: uri=str : [nbd]
 
 	Specify the NBD URI of the server to test.  The string
engines/http.c +69 -14

137 lines not on this page · raw message

fio.1 +20 -0
index 5bcb1d46..6aa23f7d 100644
@@ -2648,6 +2648,26 @@ Enable verbose requests from libcurl. Useful for debugging. 1 turns on
 verbose logging from libcurl, 2 additionally enables HTTP IO tracing.
 Default is \fB0\fR
 .TP
+.BI (http)http_object_mode \fR=\fPstr
+How to structure objects for HTTP IO: block or range. Default is \fBblock\fR.
+.RS
+.RS
+.TP
+.B block
+One object is created for every block. The HTTP engine treats \fBblocksize\fR
+as the size of the object to read or write, and appends the block start/end
+offsets to the \fBfilename\fR to create the target object path. Reads and
+writes operate on whole objects at a time.
+.TP
+.B range
+One object is created for every file. The object path is the filename directly
+for both read and write I/O. For read requests, the \fBblocksize\fR and
+\fBoffset\fR will be used to set the "Range" header on read requests to issue
+partial reads of the object. For write requests, blocksize is used to set the
+size of the object, the same as in \fBblock\fR mode.
+.RE
+.RE
+.TP
 .BI (mtd)skip_bad \fR=\fPbool
 Skip operations against known bad blocks.
 .TP