Uses of Annotation Type
org.jctools.util.InternalAPI
Packages that use InternalAPI
Package
Description
This package aims to fill a gap in current JDK implementations in offering lock free (wait free where possible)
queues for inter-thread message passing with finer grained guarantees and an emphasis on performance.
At the time of writing the only lock free queue available in the JDK is
At the time of writing the only lock free queue available in the JDK is
ConcurrentLinkedQueue
which is an unbounded multi-producer, multi-consumer queue which
is further encumbered by the need to implement the full range of Queue
methods.-
Uses of InternalAPI in org.jctools.queues
Classes in org.jctools.queues with annotations of type InternalAPIModifier and TypeClassDescriptionfinal class
A note to maintainers on index assumptions: in a single threaded world it would seem intuitive to assume:static interface
(package private) final class
This is used for method substitution in the LinkedArray classes code generation.final class
(package private) final class
(package private) final class
(package private) class
MpUnboundedXaddChunk<R,
E> interface
Tagging interface to help testing -
Uses of InternalAPI in org.jctools.util
Classes in org.jctools.util with annotations of type InternalAPIModifier and TypeInterfaceDescriptioninterface
JVM Information that is standard and available on all JVMs (i.e.final class
Power of 2 utility functions.final class
class
Why should we resort to using Unsafe?
To construct class fields which allow volatile/ordered/plain access: This requirement is covered byAtomicReferenceFieldUpdater
and similar but their performance is arguably worse than the DIY approach (depending on JVM version) while Unsafe intrinsification is a far lesser challenge for JIT compilers.interface
final class
final class