Closed carns closed 7 months ago
This issue applies to #20. See comment at https://github.com/axboe/liburing/issues/873#issuecomment-1583199242 ; liburing has a mechanism for querying a running kernel (as opposed to what's present in liburing at compile time) to see what opcodes are supported.
We could use this to select which function implementations to use on the fly, and also possibly clean up the use of preadv opcodes since it isn't necessary to set up vectors for newer kernels.
This is already implemented in origin/main now.
This issue applies to #20. See comment at https://github.com/axboe/liburing/issues/873#issuecomment-1583199242 ; liburing has a mechanism for querying a running kernel (as opposed to what's present in liburing at compile time) to see what opcodes are supported.
We could use this to select which function implementations to use on the fly, and also possibly clean up the use of preadv opcodes since it isn't necessary to set up vectors for newer kernels.