使用SmallRye Mutiny改造全部的异步接口 and jdk21适配 and 应用瘦身 about panamauring HOT 6 CLOSED

    protected Uni<Integer> writeUnsafeLazy(int offset, MemorySegment memorySegment) {
        if (closed.get()) {
            throw new NativeCallException("file has closed");
        }
        Uni<Integer> lazyRes = Uni.createFrom()
                .emitter((ue) -> {
                    AtomicLong userDataLazy = new AtomicLong();
                    long userData = ioUring.prep_write_and_get_user_data(writeFd(), offset, memorySegment,
                            (writeRes) -> {
                                ue.complete(writeRes);
                            });
                    if (userData == IOUring.NO_SQE) {
                        ue.fail(new NotEnoughSqeException());
                        return;
                    }
                    ue.context().put(USER_DATA_KEY, userData);
                    userDataLazy.set(userData);
                });

        return lazyRes.withContext((uni, c) -> {
            Long userData = c.get(USER_DATA_KEY);
// uni.onCancellation() .call(() -> eventLoop.cancelAsync(userData, 0, true));
// 这个call的语义是The upstream is not cancelled yet, but will be cancelled when the returned {@link Uni} completes
// 所以无论是否取消成功他都会设置流为取消状态
//思考这样一个场景，MemorySement为一池化内存，下游在cancel的回调里面设置当cancel时归还内存
//此时发起取消，但是此时已经进去写fd的环节导致取消失败，但是由于直接设置流为cancel 内存可以被复用了，
//此时有个其余的线程拿到了这个MemorySegement并进行写入操作，此时os仍在写入fd，写入的东西就是不可预知的了
            return uni.onCancellation()
                    .call(() -> eventLoop.cancelAsync(userData, 0, true));
        });
    }

public interface OwnershipMemory {
    MemorySegment resource();
    
    void drop();
}