Skip to contentSkip to conversation

Recent changes (master)

PATCH Jens Axboe 1 participant 1 message May 8, 2025

lore
Share & tools
lore

Jens Axboe

author
#0 lore raw

The following changes since commit 4dc6c8da6ed938f12a42f167839100ab551ae8d1:

t/zbd: add run-tests-against-scsi_debug (2025-05-07 05:28:47 -0600)

are available in the Git repository at:

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

for you to fetch changes up to 1276068fa9ecfede2fcfb2068f4670a553a6dfa4:

Merge branch 'continue_on_error_fix_up' of https://github.com/kawasaki/fio (2025-05-07 19:18:57 -0600)

----------------------------------------------------------------
Avritt Rohwer (1):
Document expected filename format for s3 http engine.

Jens Axboe (3):
Merge branch 'patch-1' of https://github.com/avrittrohwer/fio
HOWTO: fix bad whitespace
Merge branch 'continue_on_error_fix_up' of https://github.com/kawasaki/fio

Shin'ichiro Kawasaki (1):
oslib: blkzoned: add missing blkzoned_move_zone_wp() stub

 HOWTO.rst            | 5 ++++-
 README.rst           | 4 ++++
 examples/http-s3.fio | 7 +++++++
 oslib/blkzoned.h     | 6 ++++++
 4 files changed, 21 insertions(+), 1 deletion(-)

---

Diff of recent changes:

HOWTO.rst +4 -1
index a7e2f693..a5033d82 100644
@@ -808,7 +808,10 @@ Target file/device
 	For HTTP and S3 access, specify a valid URL path or S3 key, respectively.
 	A filename for path-style S3 includes a bucket name (:file:`/bucket/k/e.y`)
 	while a virtual-hosted-style S3 filename :file:`/k/e.y` does not because 
-	its bucket name is specified in :option:`http_host`.
+	its bucket name is specified in :option:`http_host`. In both cases, the
+	filename should begin with a ``/``. The HTTP engine does not automatically
+	add a leading ``/`` when constructing URLs from :option:`http_host` and
+	:option:`filename`.
 
 	The filename "`-`" is a reserved name, meaning *stdin* or *stdout*.  Which
 	of the two depends on the read/write direction set.
README.rst +4 -0
index e672ce64..c4688921 100644
@@ -165,6 +165,10 @@ Configure will attempt to determine the target platform automatically.
 It's possible to build fio for ESX as well, use the ``--esx`` switch to
 configure.
 
+The HTTP engine is enabled depending on if the curl and openssl shared libraries
+are detected on the system. For Ubuntu, these packages are libcurl4-openssl-dev
+and libssl-dev.
+
 
 Windows
 ~~~~~~~
examples/http-s3.fio +7 -0
index c16e89b1..043426ba 100644
@@ -9,6 +9,13 @@
 # For path-style, prefix the key with the bucket name in the filename
 # so that filename=/bucket-name/k/e.y:
 # https://s3.region-code.amazonaws.com/bucket-name/k/e.y
+#
+# IMPORTANT: filename needs to begin with a '/':
+# FIO formats the url as `"http://%s%s", o->host, object`, so if 
+# filename does not begin with a '/' DNS will fail. For example, if
+# http_host=amazonaws.com and filename=k/1, URL will be set to 
+# amazonaws.comk/1 and curl will attempt to resolve amazonaws.comk
+# which will fail.
 
 # Reference for Virtual-hosted-style vs. Path-style URLs:
 # https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html
oslib/blkzoned.h +6 -0
index 3a4c73c2..a8e4a948 100644
@@ -54,6 +54,12 @@ static inline int blkzoned_reset_wp(struct thread_data *td, struct fio_file *f,
 {
 	return -EIO;
 }
+static inline int blkzoned_move_zone_wp(struct thread_data *td,
+					struct fio_file *f, struct zbd_zone *z,
+					uint64_t length, const char *buf)
+{
+	return -EIO;
+}
 static inline int blkzoned_get_max_open_zones(struct thread_data *td, struct fio_file *f,
 					      unsigned int *max_open_zones)
 {