Ping QiuandClaude Opus 4.6 003b8c2f28 fix: require explicit build tags for io_uring backends, add implementation logging ...

All three io_uring backends (iceber, giouring, raw) now require explicit
build tags — no tag means standard-only. Each backend registers its name
via IOUringImpl so startup logs show compiled implementation alongside
requested/selected backend mode.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-10 18:19:31 -07:00

..

batchio.go

fix: require explicit build tags for io_uring backends, add implementation logging

2026-03-10 18:19:31 -07:00

fdatasync_linux.go

fix: BatchIO review fixes — linked SQE, ring overflow, resource leak, sync parity

2026-03-10 15:47:03 -07:00

fdatasync_other.go

fix: BatchIO review fixes — linked SQE, ring overflow, resource leak, sync parity

2026-03-10 15:47:03 -07:00

iouring_giouring_linux.go

fix: require explicit build tags for io_uring backends, add implementation logging

2026-03-10 18:19:31 -07:00

iouring_iceber_linux.go

fix: require explicit build tags for io_uring backends, add implementation logging

2026-03-10 18:19:31 -07:00

iouring_other.go

fix: require explicit build tags for io_uring backends, add implementation logging

2026-03-10 18:19:31 -07:00

iouring_raw_linux.go

fix: require explicit build tags for io_uring backends, add implementation logging

2026-03-10 18:19:31 -07:00

standard_test.go

feat: tri-state IOBackend config with explicit logging and CLI flag

2026-03-10 16:02:30 -07:00

standard.go

fix: BatchIO review fixes — linked SQE, ring overflow, resource leak, sync parity

2026-03-10 15:47:03 -07:00