An arena has a scope - the arena scope. All the segments allocated by the arena are associated with the arena scope. As such, the arena determines the temporal bounds of all the memory segments allocated by it.
Moreover, an arena also determines whether access to memory segments allocated by it
should be restricted to specific
threads. An arena is a SegmentAllocator
and features several allocation
methods that can be used by clients to obtain native segments.
The simplest arena is the global arena. The global arena features an unbounded lifetime. The scope of the global arena is the global scope. As such, native segments allocated with the global arena are always accessible and their backing regions of memory are never deallocated. Moreover, memory segments allocated with the global arena can be accessed from any thread.
MemorySegment segment = Arena.global().allocate(100, 1); ... // segment is never deallocated!
Alternatively, clients can obtain an automatic arena, that is an arena which features a bounded lifetime that is managed, automatically, by the garbage collector. The scope of an automatic arena is an automatic scope. As such, the regions of memory backing memory segments allocated with the automatic arena are deallocated at some unspecified time after the automatic arena (and all the segments allocated by it) becomes unreachable, as shown below:
MemorySegment segment = Arena.ofAuto().allocate(100, 1); ... segment = null; // the segment region becomes available for deallocation after this point
Rather than leaving deallocation in the hands of the Java runtime, clients will often wish to exercise control over the timing of deallocation for regions of memory that back memory segments. Two kinds of arenas support this, namely confined and shared arenas. They both feature bounded lifetimes that are managed manually. For instance, when a confined arena is closed successfully, its scope is invalidated. As a result, all the memory segments allocated by the arena can no longer be accessed, and their regions of memory are deallocated:
MemorySegment segment = null; try (Arena arena = Arena.ofConfined()) { segment = arena.allocate(100); ... } // segment region deallocated here segment.get(ValueLayout.JAVA_BYTE, 0); // throws IllegalStateException
The characteristics of the various arenas are summarized in the following table:
Kind Bounded lifetime Explicitly closeable Accessible from multiple threads Global No No Yes Automatic Yes No Yes Confined Yes Yes No Shared Yes Yes Yes
Conversely, if an arena allocates segments that can be accessed by multiple threads, or if the arena can be closed by a thread other than the accessing thread, then ensuring correctness is much more complex. For example, a segment allocated with the arena might be accessed while another thread attempts, concurrently, to close the arena. To provide the strong temporal safety guarantee without forcing every client, even simple ones, to incur a performance impact, arenas are divided into thread-confined arenas, and shared arenas.
Confined arenas, support strong thread-confinement guarantees. Upon creation, they are
assigned an owner thread, typically the thread which initiated the creation
operation. The segments created by a confined arena can only be
accessed by the owner thread.
Moreover, any attempt to close the confined arena from a thread other than the owner
thread will fail with a WrongThreadException
.
Shared arenas, on the other hand, have no owner thread. The segments created by a shared arena can be accessed by any thread. This might be useful when multiple threads need to access the same memory segment concurrently (e.g. in the case of parallel processing). Moreover, a shared arena can be closed by any thread.
class SlicingArena implements Arena { final Arena arena = Arena.ofConfined(); final SegmentAllocator slicingAllocator; SlicingArena(long size) { slicingAllocator = SegmentAllocator.slicingAllocator(arena.allocate(size)); } public MemorySegment allocate(long byteSize, long byteAlignment) { return slicingAllocator.allocate(byteSize, byteAlignment); } public MemorySegment.Scope scope() { return arena.scope(); } public void close() { arena.close(); } }
try (Arena slicingArena = new SlicingArena(1000)) { for (int i = 0; i < 10; i++) { MemorySegment s = slicingArena.allocateFrom(JAVA_INT, 1, 2, 3, 4, 5); ... } } // all memory allocated is released here
Implementation Specification
Implementations of this interface are thread-safe.
MemorySegment
Modifier and Type | Method and Description |
---|---|
public MemorySegment | Returns: a new native memory segmentthe size (in bytes) of the off-heap region of memory backing
the native memory segment byteSize, long the alignment constraint (in bytes) of the off-heap region
of memory backing the native memory segment byteAlignment)Redeclares java. Returns a native memory segment with the given size (in bytes) and alignment constraint (in bytes). |
public void | |
public static Arena | |
public static Arena | Returns: a new arena that is managed, automatically, by the garbage collectorCreates a new arena that is managed, automatically, by the garbage collector. |
public static Arena | |
public static Arena | |
public MemorySegment. |
allocate | back to summary |
---|---|
public MemorySegment allocate(long byteSize, long byteAlignment) Redeclares java. Returns a native memory segment with the given size (in bytes) and alignment
constraint (in bytes).
The returned segment is associated with this arena scope.
The segment's Implementation Specification Implementations of this method must return a native segment featuring the
requested size, and that is compatible with the provided alignment constraint.
Furthermore, for any two segments S1.asOverlappingSlice(S2).isEmpty() == true
|
close | back to summary |
---|---|
public void close() Redeclares java. Closes this arena. If this method completes normally, the arena scope is no longer alive, and all the memory segments associated with it can no longer be accessed. Furthermore, any off-heap region of memory backing the segments obtained from this arena are also released. API Note This operation is not idempotent; that is, closing an already closed arena always results in an exception being thrown. This reflects a deliberate design choice: failure to close an arena might reveal a bug in the underlying application logic. Implementation Specification If this method completes normally, then
|
global | back to summary |
---|---|
public static Arena global() Returns the global arena. Segments allocated with the global arena can be
accessed by any thread.
Calling Memory segments allocated by the returned arena are zero-initialized.
|
ofAuto | back to summary |
---|---|
public static Arena ofAuto() Creates a new arena that is managed, automatically, by the garbage collector.
Segments allocated with the returned arena can be
accessed by any thread.
Calling Memory segments allocated by the returned arena are zero-initialized.
|
ofConfined | back to summary |
---|---|
public static Arena ofConfined() Returns a new confined arena. Segments allocated with the confined arena can be accessed by the thread that created the arena, the arena's owner thread. Memory segments allocated by the returned arena are zero-initialized.
|
ofShared | back to summary |
---|---|
public static Arena ofShared() Returns a new shared arena. Segments allocated with the shared arena can be accessed by any thread. Memory segments allocated by the returned arena are zero-initialized.
|
scope | back to summary |
---|---|
public MemorySegment. Returns the arena scope.
|