[GitHub] [activemq-artemis-native] clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass

clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass URL: https://github.com/apache/activemq-artemis-native/pull/5#issuecomment-54766 Isn't there a new API that would perform the proper ring operations now? I understand you

[GitHub] [activemq-artemis-native] clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass

clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass URL: https://github.com/apache/activemq-artemis-native/pull/5#issuecomment-547567197 From what I understand from the ring-queue implementation, the barrier is to prevent two

[GitHub] [activemq-artemis-native] clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass

clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass URL: https://github.com/apache/activemq-artemis-native/pull/5#issuecomment-547558006 @franz1981 Can't we leave this as is? looking on it now it seems :::memory is an instruction

[GitHub] [activemq-artemis-native] clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass

clebertsuconic commented on issue #5: ARTEMIS-2533 Support multiple architecture for ASYNCIO kernel by-pass URL: https://github.com/apache/activemq-artemis-native/pull/5#issuecomment-547533913 @franz1981 I have been using ./scripts/compile-using-docker.sh to compile upstream. As