New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support IO_URING transport #4163
Comments
There are some test failures related missing public final ChannelFuture sendFile(RandomAccessFile raf, long offset, long length) throws IOException {
// Write the content.
ChannelPromise writeFuture = chctx.newPromise();
if (!supportsFileRegion()) {
// Cannot use zero-copy
writeToChannel(new ChunkedFile(raf, offset, length, 8192), writeFuture);
} else {
// No encryption - use zero-copy.
sendFileRegion(raf, offset, length, writeFuture);
}
if (writeFuture != null) {
writeFuture.addListener(fut -> raf.close());
} else {
raf.close();
}
return writeFuture;
} The downside is that |
I've fixed #4163 (comment) with franz1981@4eafe9f |
Just FYI this is the last run:
And many of these tests shouldn't run because are using domain socket, that's still not supported I'm going to prepare a draft PR ASAP |
Thank you for looking into this. It's great to have feedback and a
contribution in the making!
… |
The transport should be optional and only used when the jar is present on the classpath and native epoll is not present |
Haven't checked the latest version of the code, but that's how it was working when I tested an early preview. |
I'm implementing support for https://github.com/netty/netty-incubator-transport-io_uring on Vert-x
Transport
, see https://github.com/franz1981/vert.x/tree/4.2.1_iouring for some initial experiment.The text was updated successfully, but these errors were encountered: