US20230350802A1

US20230350802A1 - Managing lifecycles of sets of foreign resources

Info

Publication number: US20230350802A1
Application number: US17/733,258
Authority: US
Inventors: Maurizio Cimadamore; Paul David Sandoz
Original assignee: Oracle International Corp
Current assignee: Oracle International Corp
Priority date: 2022-04-29
Filing date: 2022-04-29
Publication date: 2023-11-02

Abstract

Techniques for managing lifecycles of sets of foreign resources are disclosed, including: opening, in a runtime environment configured to use a garbage collector to manage memory in a heap, a memory session; allocating a first subset of a set of foreign memory to a memory segment associated with the memory session, the foreign memory including off-heap memory that is not managed by the garbage collector; encountering, in the runtime environment, an instruction to close the memory session; responsive to encountering the instruction to close the memory session, deallocating the subset of the set of foreign memory.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to co-pending U.S. Patent Application (Attorney Docket No. R00694NP), titled “Managing Temporal Dependencies Between Sets of Foreign Resources” and filed on even date herewith, the entire contents of which are hereby incorporated by reference.
This application includes subject matter that is related to subject matter disclosed in co-pending U.S. patent application Ser. No. 17/038,766 (Attorney Docket No. R00558NP), titled “Techniques for Accessing Off-Heap Memory” and filed on Sep. 30, 2020, the entire contents of which are hereby incorporated by reference.
This application includes subject matter that is related to subject matter disclosed in co-pending U.S. patent application Ser. No. 17/024,209 (Attorney Docket No. R00563NP), titled “Transitioning Between Thread-Confined Memory Segment Views and Shared Memory Segment Views” and filed on Sep. 17, 2020, the entire contents of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to resource management in computer systems. In particular, the present disclosure relates to managing lifecycles of sets of foreign resources such as off-heap memory.

BACKGROUND

A runtime environment uses a heap, which is an area of memory from which memory is allocated for runtime data (e.g., class instances, arrays, etc.). The runtime environment includes a garbage collector that monitors the heap and frees memory that is no longer in use (e.g., memory allocated to objects to which there are no longer any strong references). For example, the Java Runtime Environment (JRE) includes a Java Virtual Machine (JVM) that uses a garbage collector to manage data stored in the Java heap.
In some cases, a program executing in the runtime environment seeks to use “foreign” resources, i.e., off-heap memory that the garbage collector does not manage. Foreign resources may be “native” to the operating environment that hosts the runtime environment. For example, native memory buffers, native function pointers, etc. are “foreign” resources because they occupy off-heap memory that the garbage collector does not manage.
Because the garbage collector does not manage foreign resources, it is important for program code executing in the runtime environment to keep track of when foreign resources are no longer in use. Failure to deallocate foreign resources that are no longer in use can result in memory leaks and/or unstable system behavior.
The approaches described in this section are approaches that could be pursued, but not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings. References to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment and mean at least one. In the drawings:

FIG. 1 illustrates an example computing architecture in which techniques described herein may be practiced.

FIG. 2 is a block diagram illustrating one embodiment of a computer system suitable for implementing methods and features described herein.

FIG. 3 illustrates an example virtual machine memory layout in block diagram form according to an embodiment.

FIG. 4 illustrates an example frame in block diagram form according to an embodiment.

FIG. 5 shows a block diagram that illustrates an example of a system in accordance with one or more embodiments;

FIG. 6 illustrates an example set of operations for managing lifecycles of sets of foreign resources in accordance with one or more embodiments;

FIGS. 7A-7C illustrate examples of managing lifecycles of sets of foreign resources in accordance with one or more embodiments; and

FIG. 8 shows a block diagram that illustrates a computer system in accordance with one or more embodiments.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation and to provide a thorough understanding, numerous specific details are set forth. One or more embodiments may be practiced without these specific details. Features described in one embodiment may be combined with features described in a different embodiment. In some examples, well-known structures and devices are described with reference to a block diagram form, in order to avoid unnecessarily obscuring the present invention.
The following table of contents is provided for reference purposes only and should not be construed as limiting the scope of one or more embodiments.

- 1. GENERAL OVERVIEW
- 2. ARCHITECTURAL OVERVIEW
- 2.1. EXAMPLE ARCHITECTURE
- 2.2. EXAMPLE CLASS FILE STRUCTURE
- 2.3. EXAMPLE VIRTUAL MACHINE ARCHITECTURE
- 2.4. LOADING, LINKING, AND INITIALIZING
- 3. EXAMPLE SYSTEM
- 3.1. SYSTEM COMPONENTS
- 3.2. USER INTERFACE
- 4. MANAGING LIFECYCLES OF SETS OF FOREIGN RESOURCES
- 5. EXAMPLE EMBODIMENTS
- 5.1. MEMORY SESSION AND SEGMENT LIFECYCLES
- 5.2. CONFINED, SHARED, AND IMPLICIT MEMORY SESSIONS
- 5.3. USER-SPECIFIED CLEANUP ACTIONS
- 6. COMPUTER NETWORKS AND CLOUD NETWORKS
- 7. HARDWARE OVERVIEW
- 8. MISCELLANEOUS; EXTENSIONS

1. General Overview

One or more embodiments manage lifecycles of sets of foreign resources (e.g., off-heap memory, native function pointers, etc.). A runtime environment opens a memory session and allocates one or more subsets of a set of foreign memory to one or more respective memory segments. Because each memory segment is associated with the memory session, closing the memory session deallocates the foreign memory allocated to the segment(s). Thus, terminating the lifecycle of the memory session also terminates the lifecycle of the foreign memory within the runtime environment. This lifecycle dependency helps ensure that unused foreign memory does not linger in the runtime environment and potentially cause a memory leak and/or unstable system behavior. One or more embodiments may close memory sessions explicitly (i.e., responsive to an explicit instruction to close a memory session) and/or implicitly (for example, by registering a memory session against a cleaner that closes the memory session when it determines that there are no longer any strong references to the memory session). Implicit closure helps protect against programming that fails to explicitly close a memory session that is no longer in use.
One or more embodiments described in this Specification and/or recited in the claims may not be included in this General Overview section.

2. Architectural Overview

2.1. Example Architecture

FIG. 1 illustrates an example architecture in which techniques described herein may be practiced. Software and/or hardware components described with relation to the example architecture may be omitted or associated with a different set of functionality than described herein. Software and/or hardware components, not described herein, may be used within an environment in accordance with one or more embodiments. Accordingly, the example environment should not be constructed as limiting the scope of any of the claims.
As illustrated in FIG. 1 , a computing architecture 100 includes source code files 101 which are compiled by a compiler 102 into class files 103 representing the program to be executed. The class files 103 are then loaded and executed by an execution platform 112, which includes a runtime environment 113, an operating system 111, and one or more application programming interfaces (APIs) 110 that enable communication between the runtime environment 113 and the operating system 111. The runtime environment 113 includes a virtual machine 104 comprising various components, such as a memory manager 105 (which may include a garbage collector), a class file verifier 106 to check the validity of class files 103, a class loader 107 to locate and build in-memory representations of classes, an interpreter 108 for executing the virtual machine 104 code, and a just-in-time (JIT) compiler 109 for producing optimized machine-level code.
In an embodiment, the computing architecture 100 includes source code files 101 that contain code that has been written in a particular programming language, such as Java, C, C++, C#, Ruby, Perl, and so forth. Thus, the source code files 101 adhere to a particular set of syntactic and/or semantic rules for the associated language. For example, code written in Java adheres to the Java Language Specification. However, since specifications are updated and revised over time, the source code files 101 may be associated with a version number indicating the revision of the specification to which the source code files 101 adhere. The exact programming language used to write the source code files 101 is generally not critical.
In various embodiments, the compiler 102 converts the source code, which is written according to a specification directed to the convenience of the programmer, to either machine or object code, which is executable directly by the particular machine environment, or an intermediate representation (“virtual machine code/instructions”), such as bytecode, which is executable by a virtual machine 104 that is capable of running on top of a variety of particular machine environments. The virtual machine instructions are executable by the virtual machine 104 in a more direct and efficient manner than the source code. Converting source code to virtual machine instructions includes mapping source code functionality from the language to virtual machine functionality that utilizes underlying resources, such as data structures. Often, functionality that is presented in simple terms via source code by the programmer is converted into more complex steps that map more directly to the instruction set supported by the underlying hardware on which the virtual machine 104 resides.
In general, programs are executed either as a compiled or an interpreted program. When a program is compiled, the code is transformed globally from a first language to a second language before execution. Since the work of transforming the code is performed ahead of time; compiled code tends to have excellent run-time performance. In addition, since the transformation occurs globally before execution, the code can be analyzed and optimized using techniques such as constant folding, dead code elimination, inlining, and so forth. However, depending on the program being executed, the startup time can be significant. In addition, inserting new code would require the program to be taken offline, re-compiled, and re-executed. For many dynamic languages (such as Java) which are designed to allow code to be inserted during the program's execution, a purely compiled approach may be inappropriate. When a program is interpreted, the code of the program is read line-by-line and converted to machine-level instructions while the program is executing. As a result, the program has a short startup time (can begin executing almost immediately), but the run-time performance is diminished by performing the transformation on the fly. Furthermore, since each instruction is analyzed individually, many optimizations that rely on a more global analysis of the program cannot be performed.
In some embodiments, the virtual machine 104 includes an interpreter 108 and a JIT compiler 109 (or a component implementing aspects of both), and executes programs using a combination of interpreted and compiled techniques. For example, the virtual machine 104 may initially begin by interpreting the virtual machine instructions representing the program via the interpreter 108 while tracking statistics related to program behavior, such as how often different sections or blocks of code are executed by the virtual machine 104. Once a block of code surpasses a threshold (is “hot”), the virtual machine 104 invokes the JIT compiler 109 to perform an analysis of the block and generate optimized machine-level instructions which replaces the “hot” block of code for future executions. Since programs tend to spend most time executing a small portion of overall code, compiling just the “hot” portions of the program can provide similar performance to fully compiled code, but without the start-up penalty. Furthermore, although the optimization analysis is constrained to the “hot” block being replaced, there still exists far greater optimization potential than converting each instruction individually. There are a number of variations on the above described example, such as tiered compiling.
In order to provide clear examples, the source code files 101 have been illustrated as the “top level” representation of the program to be executed by the execution platform 112. Although the computing architecture 100 depicts the source code files 101 as a “top level” program representation, in other embodiments the source code files 101 may be an intermediate representation received via a “higher level” compiler that processed code files in a different language into the language of the source code files 101. Some examples in the following disclosure assume that the source code files 101 adhere to a class-based object-oriented programming language. However, this is not a requirement to utilizing the features described herein.
In an embodiment, compiler 102 receives as input the source code files 101 and converts the source code files 101 into class files 103 that are in a format expected by the virtual machine 104. For example, in the context of the JVM, the Java Virtual Machine Specification defines a particular class file format to which the class files 103 are expected to adhere. In some embodiments, the class files 103 contain the virtual machine instructions that have been converted from the source code files 101. However, in other embodiments, the class files 103 may contain other structures as well, such as tables identifying constant values and/or metadata related to various structures (classes, fields, methods, and so forth).
The following discussion assumes that each of the class files 103 represents a respective “class” defined in the source code files 101 (or dynamically generated by the compiler 102/ virtual machine 104 ). However, the aforementioned assumption is not a strict requirement and will depend on the implementation of the virtual machine 104. Thus, the techniques described herein may still be performed regardless of the exact format of the class files 103. In some embodiments, the class files 103 are divided into one or more “libraries” or “packages”, each of which includes a collection of classes that provide related functionality. For example, a library may contain one or more class files that implement input/output (I/O) operations, mathematics tools, cryptographic techniques, graphics utilities, and so forth. Further, some classes (or fields/methods within those classes) may include access restrictions that limit their use to within a particular class/library/package or to classes with appropriate permissions.

2.2. Example Class File Structure

FIG. 2 illustrates an example structure for a class file 200 in block diagram form according to an embodiment. In order to provide clear examples, the remainder of the disclosure assumes that the class files 103 of the computing architecture 100 adhere to the structure of the example class file 200 described in this section. However, in a practical environment, the structure of the class file 200 will be dependent on the implementation of the virtual machine 104. Further, one or more features discussed herein may modify the structure of the class file 200 to, for example, add additional structure types. Therefore, the exact structure of the class file 200 is not critical to the techniques described herein. For the purposes of Section 2.1, “the class” or “the present class” refers to the class represented by the class file 200.
In FIG. 2 , the class file 200 includes a constant table 201, field structures 208, class metadata 207, and method structures 209. In an embodiment, the constant table 201 is a data structure which, among other functions, acts as a symbol table for the class. For example, the constant table 201 may store data related to the various identifiers used in the source code files 101 such as type, scope, contents, and/or location. The constant table 201 has entries for value structures 202 (representing constant values of type int, long, double, float, byte, string, and so forth), class information structures 203, name and type information structures 204, field reference structures 205, and method reference structures 206 derived from the source code files 101 by the compiler 102. In an embodiment, the constant table 201 is implemented as an array that maps an index i to structure j. However, the exact implementation of the constant table 201 is not critical.
In some embodiments, the entries of the constant table 201 include structures which index other constant table 201 entries. For example, an entry for one of the value structures 202 representing a string may hold a tag identifying its “type” as string and an index to one or more other value structures 202 of the constant table 201 storing char, byte or int values representing the ASCII characters of the string.
In an embodiment, field reference structures 205 of the constant table 201 hold an index into the constant table 201 to one of the class information structures 203 representing the class defining the field and an index into the constant table 201 to one of the name and type information structures 204 that provides the name and descriptor of the field. Method reference structures 206 of the constant table 201 hold an index into the constant table 201 to one of the class information structures 203 representing the class defining the method and an index into the constant table 201 to one of the name and type information structures 204 that provides the name and descriptor for the method. The class information structures 203 hold an index into the constant table 201 to one of the value structures 202 holding the name of the associated class.
The name and type information structures 204 hold an index into the constant table 201 to one of the value structures 202 storing the name of the field/method and an index into the constant table 201 to one of the value structures 202 storing the descriptor.
In an embodiment, class metadata 207 includes metadata for the class, such as version number(s), number of entries in the constant pool, number of fields, number of methods, access flags (whether the class is public, private, final, abstract, etc.), an index to one of the class information structures 203 of the constant table 201 that identifies the present class, an index to one of the class information structures 203 of the constant table 201 that identifies the superclass (if any), and so forth.
In an embodiment, the field structures 208 represent a set of structures that identifies the various fields of the class. The field structures 208 store, for each field of the class, accessor flags for the field (whether the field is static, public, private, final, etc.), an index into the constant table 201 to one of the value structures 202 that holds the name of the field, and an index into the constant table 201 to one of the value structures 202 that holds a descriptor of the field.
In an embodiment, the method structures 209 represent a set of structures that identifies the various methods of the class. The method structures 209 store, for each method of the class, accessor flags for the method (e.g. whether the method is static, public, private, synchronized, etc.), an index into the constant table 201 to one of the value structures 202 that holds the name of the method, an index into the constant table 201 to one of the value structures 202 that holds the descriptor of the method, and the virtual machine instructions that correspond to the body of the method as defined in the source code files 101.
In an embodiment, a descriptor represents a type of a field or method. For example, the descriptor may be implemented as a string adhering to a particular syntax. While the exact syntax is not critical, a few examples are described below.
In an example where the descriptor represents a type of the field, the descriptor identifies the type of data held by the field. In an embodiment, a field can hold a basic type, an object, or an array. When a field holds a basic type, the descriptor is a string that identifies the basic type (e.g., “B”=byte, “C”=char, “D”=double, “F”=float, “I”=int, “J” =long int, etc.). When a field holds an object, the descriptor is a string that identifies the class name of the object (e.g. “L ClassName”). “L” in this case indicates a reference, thus “L ClassName” represents a reference to an object of class ClassName. When the field is an array, the descriptor identifies the type held by the array. For example, “[B” indicates an array of bytes, with “[” indicating an array and “B” indicating that the array holds the basic type of byte. However, since arrays can be nested, the descriptor for an array may also indicate the nesting. For example, “[[L ClassName” indicates an array where each index holds an array that holds objects of class ClassName. In some embodiments, the ClassName is fully qualified and includes the simple name of the class, as well as the pathname of the class. For example, the ClassName may indicate where the file is stored in the package, library, or file system hosting the class file 200.
In the case of a method, the descriptor identifies the parameters of the method and the return type of the method. For example, a method descriptor may follow the general form “({ParameterDescriptor}) ReturnDescriptor”, where the {ParameterDescriptor} is a list of field descriptors representing the parameters and the ReturnDescriptor is a field descriptor identifying the return type. For instance, the string “V” may be used to represent the void return type. Thus, a method defined in the source code files 101 as “Object m(int I, double d, Thread t) {. . . }” matches the descriptor “(I D L Thread) L Object”.
In an embodiment, the virtual machine instructions held in the method structures 209 include operations which reference entries of the constant table 201. Using Java as an example, consider the following class:


	class A
	{
	int add12and13( ) {
	return B.addTwo(12, 13);
	}
	}

In the above example, the Java method add12and13 is defined in class A, takes no parameters, and returns an integer. The body of method add12and13 calls static method addTwo of class B which takes the constant integer values 12 and 13 as parameters, and returns the result. Thus, in the constant table 201, the compiler 102 includes, among other entries, a method reference structure that corresponds to the call to the method B.addTwo. In Java, a call to a method compiles down to an invoke command in the bytecode of the JVM (in this case invokestatic as addTwo is a static method of class B). The invoke command is provided an index into the constant table 201 corresponding to the method reference structure that identifies the class defining addTwo “B”, the name of addTwo “addTwo”, and the descriptor of addTwo “(I I)I”. For example, assuming the aforementioned method reference is stored at index 4, the bytecode instruction may appear as “invokestatic #4”.
Since the constant table 201 refers to classes, methods, and fields symbolically with structures carrying identifying information, rather than direct references to a memory location, the entries of the constant table 201 are referred to as “symbolic references”. One reason that symbolic references are utilized for the class files 103 is because, in some embodiments, the compiler 102 is unaware of how and where the classes will be stored once loaded into the runtime environment 113. As will be described in Section 2.3, eventually the run-time representations of the symbolic references are resolved into actual memory addresses by the virtual machine 104 after the referenced classes (and associated structures) have been loaded into the runtime environment and allocated concrete memory locations.

2.3. Example Virtual Machine Architecture

FIG. 3 illustrates an example virtual machine memory layout 300 in block diagram form according to an embodiment. In order to provide clear examples, the remaining discussion will assume that the virtual machine 104 adheres to the virtual machine memory layout 300 depicted in FIG. 3 . In addition, although components of the virtual machine memory layout 300 may be referred to as memory “areas”, there is no requirement that the memory areas are contiguous.
In the example illustrated by FIG. 3 , the virtual machine memory layout 300 is divided into a shared area 301 and a thread area 307. The shared area 301 represents an area in memory where structures shared among the various threads executing on the virtual machine 104 are stored. The shared area 301 includes a heap 302 and a per-class area 303. In an embodiment, the heap 302 represents the run-time data area from which memory for class instances and arrays is allocated. In an embodiment, the per-class area 303 represents the memory area where the data pertaining to the individual classes are stored. In an embodiment, the per-class area 303 includes, for each loaded class, a run-time constant pool 304 representing data from the constant table 201 of the class, field and method data 306 (for example, to hold the static fields of the class), and the method code 305 representing the virtual machine instructions for methods of the class.
The thread area 307 represents a memory area where structures specific to individual threads are stored. In FIG. 3 , the thread area 307 includes thread structures 308 and thread structures 311, representing the per-thread structures utilized by different threads. In order to provide clear examples, the thread area 307 depicted in FIG. 3 assumes two threads are executing on the virtual machine 104. However, in a practical environment, the virtual machine 104 may execute any arbitrary number of threads, with the number of thread structures scaled accordingly.
In an embodiment, thread structures 308 includes program counter 309 and virtual machine stack 310. Similarly, thread structures 311 includes program counter 312 and virtual machine stack 313. In an embodiment, program counter 309 and program counter 312 store the current address of the virtual machine instruction being executed by their respective threads.
Thus, as a thread steps through the instructions, the program counters are updated to maintain an index to the current instruction. In an embodiment, virtual machine stack 310 and virtual machine stack 313 each store frames for their respective threads that hold local variables and partial results, and is also used for method invocation and return.
In an embodiment, a frame is a data structure used to store data and partial results, return values for methods, and perform dynamic linking. A new frame is created each time a method is invoked. A frame is destroyed when the method that caused the frame to be generated completes. Thus, when a thread performs a method invocation, the virtual machine 104 generates a new frame and pushes that frame onto the virtual machine stack associated with the thread.
When the method invocation completes, the virtual machine 104 passes back the result of the method invocation to the previous frame and pops the current frame off of the stack. In an embodiment, for a given thread, one frame is active at any point. This active frame is referred to as the current frame, the method that caused generation of the current frame is referred to as the current method, and the class to which the current method belongs is referred to as the current class.
FIG. 4 illustrates an example frame 400 in block diagram form according to an embodiment. In order to provide clear examples, the remaining discussion will assume that frames of virtual machine stack 310 and virtual machine stack 313 adhere to the structure of frame 400.
In an embodiment, frame 400 includes local variables 401, operand stack 402, and run-time constant pool reference table 403. In an embodiment, the local variables 401 are represented as an array of variables that each hold a value, for example, Boolean, byte, char, short, int, float, or reference. Further, some value types, such as longs or doubles, may be represented by more than one entry in the array. The local variables 401 are used to pass parameters on method invocations and store partial results. For example, when generating the frame 400 in response to invoking a method, the parameters may be stored in predefined positions within the local variables 401, such as indexes 1-N corresponding to the first to Nth parameters in the invocation.
In an embodiment, the operand stack 402 is empty by default when the frame 400 is created by the virtual machine 104. The virtual machine 104 then supplies instructions from the method code 305 of the current method to load constants or values from the local variables 401 onto the operand stack 402. Other instructions take operands from the operand stack 402, operate on them, and push the result back onto the operand stack 402. Furthermore, the operand stack 402 is used to prepare parameters to be passed to methods and to receive method results. For example, the parameters of the method being invoked could be pushed onto the operand stack 402 prior to issuing the invocation to the method. The virtual machine 104 then generates a new frame for the method invocation where the operands on the operand stack 402 of the previous frame are popped and loaded into the local variables 401 of the new frame. When the invoked method terminates, the new frame is popped from the virtual machine stack and the return value is pushed onto the operand stack 402 of the previous frame.
In an embodiment, the run-time constant pool reference table 403 contains a reference to the run-time constant pool 304 of the current class. The run-time constant pool reference table 403 is used to support resolution. Resolution is the process whereby symbolic references in the constant pool 304 are translated into concrete memory addresses, loading classes as necessary to resolve as-yet-undefined symbols and translating variable accesses into appropriate offsets into storage structures associated with the run-time location of these variables.

2.4. Loading, Linking, and Initializing

In an embodiment, the virtual machine 104 dynamically loads, links, and initializes classes. Loading is the process of finding a class with a particular name and creating a representation from the associated class file 200 of that class within the memory of the runtime environment 113. For example, creating the run-time constant pool 304, method code 305, and field and method data 306 for the class within the per-class area 303 of the virtual machine memory layout 300. Linking is the process of taking the in-memory representation of the class and combining it with the run-time state of the virtual machine 104 so that the methods of the class can be executed. Initialization is the process of executing the class constructors to set the starting state of the field and method data 306 of the class and/or create class instances on the heap 302 for the initialized class.
The following are examples of loading, linking, and initializing techniques that may be implemented by the virtual machine 104. However, in many embodiments the steps may be interleaved, such that an initial class is loaded, then during linking a second class is loaded to resolve a symbolic reference found in the first class, which in turn causes a third class to be loaded, and so forth. Thus, progress through the stages of loading, linking, and initializing can differ from class to class. Further, some embodiments may delay (perform “lazily”) one or more functions of the loading, linking, and initializing process until the class is actually required. For example, resolution of a method reference may be delayed until a virtual machine instruction invoking the method is executed. Thus, the exact timing of when the steps are performed for each class can vary greatly between implementations.
To begin the loading process, the virtual machine 104 starts up by invoking the class loader 107 which loads an initial class. The technique by which the initial class is specified will vary from embodiment to embodiment. For example, one technique may have the virtual machine 104 accept a command line argument on startup that specifies the initial class.
To load a class, the class loader 107 parses the class file 200 corresponding to the class and determines whether the class file 200 is well-formed (meets the syntactic expectations of the virtual machine 104). If not, the class loader 107 generates an error. For example, in Java the error might be generated in the form of an exception which is thrown to an exception handler for processing. Otherwise, the class loader 107 generates the in-memory representation of the class by allocating the run-time constant pool 304, method code 305, and field and method data 306 for the class within the per-class area 303.
In some embodiments, when the class loader 107 loads a class, the class loader 107 also recursively loads the super-classes of the loaded class. For example, the virtual machine 104 may ensure that the super-classes of a particular class are loaded, linked, and/or initialized before proceeding with the loading, linking and initializing process for the particular class.
During linking, the virtual machine 104 verifies the class, prepares the class, and performs resolution of the symbolic references defined in the run-time constant pool 304 of the class.
To verify the class, the virtual machine 104 checks whether the in-memory representation of the class is structurally correct. For example, the virtual machine 104 may check that each class except the generic class Object has a superclass, check that final classes have no sub-classes and final methods are not overridden, check whether constant pool entries are consistent with one another, check whether the current class has correct access permissions for classes/fields/structures referenced in the constant pool 304, check that the virtual machine 104 code of methods will not cause unexpected behavior (e.g. making sure a jump instruction does not send the virtual machine 104 beyond the end of the method), and so forth. The exact checks performed during verification are dependent on the implementation of the virtual machine 104. In some cases, verification may cause additional classes to be loaded, but does not necessarily require those classes to also be linked before proceeding. For example, assume Class A contains a reference to a static field of Class B. During verification, the virtual machine 104 may check Class B to ensure that the referenced static field actually exists, which might cause loading of Class B, but not necessarily the linking or initializing of Class B. However, in some embodiments, certain verification checks can be delayed until a later phase, such as being checked during resolution of the symbolic references. For example, some embodiments may delay checking the access permissions for symbolic references until those references are being resolved.
To prepare a class, the virtual machine 104 initializes static fields located within the field and method data 306 for the class to default values. In some cases, setting the static fields to default values may not be the same as running a constructor for the class. For example, the verification process may zero out or set the static fields to values that the constructor would expect those fields to have during initialization.
During resolution, the virtual machine 104 dynamically determines concrete memory address from the symbolic references included in the run-time constant pool 304 of the class. To resolve the symbolic references, the virtual machine 104 utilizes the class loader 107 to load the class identified in the symbolic reference (if not already loaded). Once loaded, the virtual machine 104 has knowledge of the memory location within the per-class area 303 of the referenced class and its fields/methods. The virtual machine 104 then replaces the symbolic references with a reference to the concrete memory location of the referenced class, field, or method. In an embodiment, the virtual machine 104 caches resolutions to be reused in case the same class/name/descriptor is encountered when the virtual machine 104 processes another class. For example, in some cases, class A and class B may invoke the same method of class C. Thus, when resolution is performed for class A, that result can be cached and reused during resolution of the same symbolic reference in class B to reduce overhead.
In some embodiments, the step of resolving the symbolic references during linking is optional. For example, an embodiment may perform the symbolic resolution in a “lazy” fashion, delaying the step of resolution until a virtual machine instruction that requires the referenced class/method/field is executed.
During initialization, the virtual machine 104 executes the constructor of the class to set the starting state of that class. For example, initialization may initialize the field and method data 306 for the class and generate/initialize any class instances on the heap 302 created by the constructor. For example, the class file 200 for a class may specify that a particular method is a constructor that is used for setting up the starting state. Thus, during initialization, the virtual machine 104 executes the instructions of that constructor.
In some embodiments, the virtual machine 104 performs resolution on field and method references by initially checking whether the field/method is defined in the referenced class. Otherwise, the virtual machine 104 recursively searches through the super-classes of the referenced class for the referenced field/method until the field/method is located, or the top-level superclass is reached, in which case an error is generated.

3. Example System

3.1. System Components

FIG. 5 illustrates an example of a system 500 in accordance with one or more embodiments. As illustrated in FIG. 5 , the system 500 includes a runtime environment 502, program code 504, a heap 506, a garbage collector 508, a resource manager 510, foreign resources 512, and an interface 514. In one or more embodiments, the system 500 may include more or fewer components than the components illustrated in FIG. 5 . The components illustrated in FIG. 5 may be local to or remote from each other. The components illustrated in FIG. 5 may be implemented in software and/or hardware. Each component may be distributed over multiple applications and/or machines. Multiple components may be combined into one application and/or machine. Operations described with respect to one component may instead be performed by another component.
Additional embodiments and/or examples relating to computer networks are described below in the section titled “Computer Networks and Cloud Networks.”
In the example illustrated in FIG. 5 , a runtime environment 502 is configured to execute program code 504. For example, the runtime environment 502 may be a JRE and the program code 504 may include Java bytecode. The runtime environment 502 may be configured to execute the program code 504 using a virtual machine (e.g., a JVM) (not shown).
The runtime environment 502 includes components that are configured to manage resources generated and used by the program code 504. Specifically, the runtime environment 502 includes a heap 506 and a garbage collector 508. The garbage collector 508 is configured to use various garbage collection techniques to deallocate memory in the heap 506 that is no longer being used by the program code 504. For example, garbage collection techniques performed by the garbage collector 508 may include one or more of: incremental or “minor” garbage collection; full or “major” garbage collection; serial garbage collection; parallel garbage collection; concurrent mark sweep (CMS); garbage-first (G1) garbage collection; and/or other garbage collection techniques.
Foreign resources 512 are resources that occupy off-heap memory that the garbage collector 508 does not manage. Foreign resources 512 may be “native” to the operating environment that hosts the runtime environment 502. For example, native memory buffers, native function pointers, handles to open files, sockets, native libraries (e.g., using the Linux “dlopen” function to load a native library, which may be unloaded when no longer needed), etc. are “foreign” resources because they occupy off-heap memory that the garbage collector 508 does not manage. Because foreign resources 512 occupy off-heap memory, examples described herein with respect to “foreign memory” may apply to any kind of foreign resources 512.
In one or more embodiments, a resource manager 510 refers to hardware and/or software configured to perform operations described herein for managing lifecycles of sets of foreign resources 512. Some or all of the functionality of the resource manager 510 may be implemented in program code 504. Alternatively or additionally, some or all of the functionality of the resource manager 510 may be implemented as part of the runtime environment 502, independent of the program code 504. For example, the resource manager 510 may be part of a package or library that is available to the program code 504.
In one or more embodiments, one or more components of the system 500 are implemented on one or more digital devices. The term “digital device” generally refers to any hardware device that includes a processor. A digital device may refer to a physical device executing an application or a virtual machine. Examples of digital devices include a computer, a tablet, a laptop, a desktop, a netbook, a server, a web server, a network policy server, a proxy server, a generic machine, a function-specific hardware device, a hardware router, a hardware switch, a hardware firewall, a hardware firewall, a hardware network address translator (NAT), a hardware load balancer, a mainframe, a television, a content receiver, a set-top box, a printer, a mobile handset, a smartphone, a personal digital assistant (PDA), a wireless receiver and/or transmitter, a base station, a communication management device, a router, a switch, a controller, an access point, and/or a client device.

3.2. User Interface

In one or more embodiments, an interface 514 refers to hardware and/or software configured to facilitate communications between a user and the runtime environment 502. For example, the interface 514 may be part of an integrated development environment (IDE) used to generate the program code 504.
The interface 514 renders user interface elements and receives input via user interface elements. Examples of interfaces include a graphical user interface (GUI), a command line interface (CLI), a haptic interface, and a voice command interface. Examples of user interface elements include checkboxes, radio buttons, dropdown lists, list boxes, buttons, toggles, text fields, date and time selectors, command lines, sliders, pages, and forms. Different components of the interface 514 may be specified in different languages. For example, the behavior of user interface elements may be specified in a dynamic programming language, such as JavaScript. The content of user interface elements may be specified in a markup language, such as hypertext markup language (HTML) or XML User Interface Language (XUL). The layout of user interface elements may be specified in a style sheet language, such as Cascading Style Sheets (CSS). Alternatively, the interface 514 may be specified in one or more other languages, such as Java, Python, C, or C++.

4. Managing Lifecycles of Sets of Foreign Resources

FIG. 6 illustrates an example set of operations for managing lifecycles of sets of foreign resources in accordance with one or more embodiments. One or more operations illustrated in FIG. 6 may be modified, rearranged, or omitted all together. Accordingly, the particular sequence of operations illustrated in FIG. 6 should not be construed as limiting the scope of one or more embodiments.
Examples are described herein with reference to the example system illustrated in FIG. 5 . In an embodiment, the runtime environment opens a memory session (Operation 602). The memory session is an on-heap structure. The runtime environment may open the memory session responsive to an explicit instruction in code, and/or responsive to detecting a predefined runtime condition that indicates a need for foreign resources (e.g., instantiating a class that relies on a memory session).
Using an allocation function, the runtime environment allocates one or more subsets of foreign memory to one or more respective memory segments (Operation 604 ). For example, in a Java environment, the allocation function may be a method of a class used to instantiate and manage memory segments. The runtime environment may allocate a subset of foreign memory to a memory segment responsive to an explicit instruction in code, and/or responsive to detecting a predefined runtime condition that indicates a need for a memory segment. The number of memory segments needed at runtime may not be known at development or compile time. The allocation function may take, as an argument, a reference to the memory session. The allocation function may store an association between the memory segment and the memory session.
In an embodiment, the allocation function stores a reference to the memory session in a field or member variable of the memory segment; this allows for programmatically determining (e.g., by obtaining the value of the field) which session is backing the segment and then querying the session to determine whether the segment is still “alive,” i.e., backed by a session that is still open. Alternatively or additionally, for each off-heap memory segment allocated with a particular memory session, the memory session may record a set of cleanup actions for the memory segment(s) allocated within that session. When the memory session is closed, the runtime environment may execute the cleanup actions (e.g., to “free” a pointer) to free the memory backed by that session. In general, when the memory session is closed, the stored association indicates that the foreign resources allocated to the memory segment should be deallocated. In addition, closing the underlying session may render the memory segment inaccessible, thus avoiding unpredictable behavior (e.g., crashes) that might otherwise result from attempting to access a memory segment backed by a session that has already been closed.
After allocating foreign memory to one or more memory segments, the runtime environment encounters an instruction to close the memory session (Operation 608). An instruction to close a memory session may take various forms. As a first example, the memory session's class may include a function that, when called with the session as an argument, closes the memory session. As a second example, the memory session itself may include a function for closing the memory session. As a third example, the memory session's lifecycle may be bounded by a programmatic scope, such as a particular method or other block of code. The memory session may be opened in the scope of a try block (for example, a Java try-with-resources block that declares an open memory session as a resource), so that the runtime environment closes the memory session upon termination of the try block. Termination of the try block thus provides an implicit instruction to close the memory session.
As a fourth example, the memory session may be opened with implicit closure, as described in further detail below. A memory session that is opened with implicit closure may not support explicit closure, i.e., closure via a programmatic instruction to close the memory session. Rather, the memory session can be closed (and the underlying foreign resources deallocated) only when the runtime environment determines (e.g., using garbage collection techniques) that the memory session is no longer in use. Implicit closure may be slower and higher-latency than explicitly closing a memory session (e.g., if the garbage collector takes some time to determine that the memory session is not in use) but may be appropriate in some situations, such as when a memory segment is expected to be long-lived and therefore the overhead associated with implicit closure of its session is expected to be relatively low.
Responsive to encountering the instruction to close the memory session, the runtime environment determines whether any foreign resources have been allocated to any memory segment(s) associated with the memory session (Operation 606). For example, the runtime environment may determine whether the memory session's class (e.g., in a static field) and/or the memory session itself include any stored association(s) between the memory session and any memory segment(s). If any foreign resources have been allocated to any memory segment(s) associated with the memory session, then the runtime environment deallocates the foreign memory allocated to the segment(s) (Operation 608). The runtime environment closes the memory session (Operation 610).
In one or more embodiments, one or more client memory sessions may “borrow” foreign resources from a memory session while it is open, effectively forming a parent-child relationship between the memory session and the client memory session. In such cases, the runtime environment may prohibit explicit closure of the parent memory session, as long as it has any open child memory sessions. The runtime environment may nonetheless close all child memory sessions if the parent memory session ceases to be in scope. Restrictions on closing memory sessions are discussed in further detail in co-pending U.S. patent application Ser. No. ______ (Attorney Docket No. R00694NP), titled “Managing Temporal Dependencies Between Sets of Foreign Resources,” incorporated by reference above.
Techniques described herein help ensure that the lifecycles of all memory segments allocated from a particular set of foreign resources are clearly delineated. Specifically, because the memory segments are allocated in connection with the same memory session, the memory session's lifecycle provides an outer bound for the segments' respective lifecycles. The exact number of segments needed does not need to be known at development or compile-time. Program code can use any number of segments associated with the same memory session, within the delineated scope of the memory session's lifecycle, knowing that (a) the segment's allocated memory will not be unexpectedly deallocated while in use, and (b) even if the program code never explicitly closes a segment's session, the segment's memory will not remain allocated indefinitely after the intended scope of use terminates. Thus, techniques described herein provide a technical solution to the technical problem of managing lifecycles of sets of foreign resources, such as off-heap memory.

5. Example Embodiments

Detailed examples are described below for purposes of clarity. Components and/or operations described below should be understood as specific examples which may not be applicable to certain embodiments. Accordingly, components and/or operations described below should not be construed as limiting the scope of any of the claims. Specifically, FIGS. 7A-7C illustrate examples of managing lifecycles of sets of foreign resources in accordance with one or more embodiments.

5.1. Memory Session and Segment Lifecycles

Starting with FIG. 7A, in code 702, a try block starting on line 1 declares a newly opened memory session as a resource. The opening brace (line 1) and closing brace (line 6) of the try block delineate the memory session's scope, i.e., its lifecycle. Within the try block, as shown in lines 2-4, segments of foreign resources (referred to in this example as “native” memory because it is native to the operating environment) can be allocated to respective segments, with the memory session being provided as an argument to the memory segment class's allocation function. Any number of operations may be performed (line 5) within the scope of the try block, with the assurances that the segments' memory (a) will remain allocated within that scope and (b) will be deallocated once the scope terminates.
In code 702, the number of segments needed is not known at development or compile-time. The method getSegmentCount( ) retrieves a value indicating how many segments are needed, based on one or more program-specific criteria. The for loop (lines 3-5) allocates foreign resources to each of those segments. Again, any number of operations may be performed (line 6) within the scope of the try block, with the assurance that the segments' memory (a) will remain allocated within that scope and (b) will be deallocated once the scope terminates.
In code 706, the memory session's lifecycle is not delineated by a try block. Instead, the method openImplicit( ) registers a cleaner against the memory session. Allocating memory segments (lines 2-5) and executing one or more further operations (line 6) proceeds in the same manner as the example in code 704. However, instead of deallocating the segments' memory when the memory session falls out of scope, the cleaner determines when the memory session is no longer in use (for example, if there are no longer any strong references to the memory session). Once the memory session is no longer in use, it is safe to deallocate the segments' memory and close the memory session (shown here as line “X” because the cleaner performs closure implicitly, without requiring an explicit instruction).

5.2. Confined, Shared, and Implicit Memory Sessions

Turning to FIG. 7B, code 708 is an example of a memory session constructor according to an embodiment. In line 1, the constructor takes as arguments (a) an owner thread and (b) a cleaner object. If the thread is non-null, then the memory session is confined to the specified thread; otherwise, it is a shared memory session (i.e., not confined to being used by one specific thread). If the cleaner object is non-null, then the constructor registers the memory session against the provided cleaner object (lines 4-6). In this example, the ResourceList object provides a level of abstraction so that the memory session does not maintain a strong reference to itself (“this”). If the memory session did maintain a strong reference to itself, then the cleaner could never determine that the memory session is no longer is use.
Code 710 includes examples of opening memory sessions five different ways: two that open confined memory sessions; two that open shared memory sessions; and one that opens a shared memory session with implicit closure.

Confined Memory Sessions

Line 2 is an example of calling a method to open a confined memory session, with no arguments provided to the method. As shown in the comment on line 2, this method calls a memory session constructor with the current thread and no cleaner object as arguments, returning a new memory session that is (a) confined to the current thread and (b) not registered against any cleaner object.
Line 3 is an example of calling a method to open a confined memory session, with a particular cleaner object provided as an argument to the method. As shown in the comment on line 3, this method calls a memory session constructor with the current thread and the provided cleaner object as arguments, returning a new memory session that is (a) confined to the current thread and (b) registered against the provided cleaner object.

Shared Memory Sessions

Line 6 is an example of calling a method to open a shared memory session, with no arguments provided to the method. As shown in the comment on line 6, this method calls a memory session constructor with no thread and no cleaner object as arguments, returning a new memory session that is (a) shared, i.e., not confined to any particular thread and (b) not registered against any cleaner object.
Line 7 is an example of calling a method to open a shared memory session with a particular cleaner object provided as an argument to the method. As shown in the comment on line 7, this method calls a memory session constructor with no thread and the provided cleaner object as arguments, returning a new memory session that is (a) shared and (b) registered against the provided cleaner object.

Implicit Closure

Line 10 is an example of calling a method to open a memory session with implicit closure, with no arguments provided to the method. As shown in the comment on line 10, this method calls a memory session constructor with no thread and an internal cleaner object provided as arguments, returning a new memory session that is (a) shared and (b) registered against the internal cleaner object. In an embodiment, a memory session with implicit closure can be registered against a user-supplied cleaner object. Alternatively, user-supplied cleaner objects may not be supported.

5.3. User-Specified Cleanup Actions

Turning to FIG. 7C, in one or more embodiments, a specific cleanup action can be specified programmatically. Code 712 is an example of specifying a cleanup action when a library is responsible for allocation and release of memory allocated within its functions. In line 1, the call to the method createContext( ) returns a raw pointer of type MemoryAddress. The try block starting on line 2 declares a confined memory session as a resource. Inside the scope of the try block, a segment is created from the raw address, associating spatial bounds as well as a session. Line 4 specifies a cleanup action, so that when the memory session is closed, the library destroys the memory associated with the context pointer. When the try block terminates, the memory session is closed, triggering the cleanup action. The cleanup action releases the memory associated with the library-managed “context” address.

6. Computer Networks and Cloud Networks

In one or more embodiments, a computer network provides connectivity among a set of nodes. The nodes may be local to and/or remote from each other. The nodes are connected by a set of links. Examples of links include a coaxial cable, an unshielded twisted cable, a copper cable, an optical fiber, and a virtual link.
A subset of nodes implements the computer network. Examples of such nodes include a switch, a router, a firewall, and a network address translator (NAT). Another subset of nodes uses the computer network. Such nodes (also referred to as “hosts”) may execute a client process and/or a server process. A client process makes a request for a computing service, such as execution of a particular application and/or storage of a particular amount of data). A server process responds by, for example, executing the requested service and/or returning corresponding data.
A computer network may be a physical network, including physical nodes connected by physical links. A physical node is any digital device. A physical node may be a function-specific hardware device, such as a hardware switch, a hardware router, a hardware firewall, or a hardware NAT. Additionally or alternatively, a physical node may be a generic machine that is configured to execute various virtual machines and/or applications performing respective functions. A physical link is a physical medium connecting two or more physical nodes. Examples of links include a coaxial cable, an unshielded twisted cable, a copper cable, and an optical fiber.
A computer network may be an overlay network. An overlay network is a logical network implemented on top of another network, such as a physical network. Each node in an overlay network corresponds to a respective node in the underlying network. Hence, each node in an overlay network is associated with both an overlay address (to address to the overlay node) and an underlay address (to address the underlay node that implements the overlay node). An overlay node may be a digital device and/or a software process (such as a virtual machine, an application instance, or a thread) A link that connects overlay nodes is implemented as a tunnel through the underlying network. The overlay nodes at either end of the tunnel treat the underlying multi-hop path between them as a single logical link. Tunneling is performed through encapsulation and decapsulation.
A client may be local to and/or remote from a computer network. The client may access the computer network over other computer networks, such as a private network or the Internet. The client may communicate requests to the computer network using a communications protocol, such as Hypertext Transfer Protocol (HTTP). The requests are communicated through an interface, such as a client interface (for example, a web browser), a program interface, or an application programming interface (API).
In one or more embodiments, a computer network provides connectivity between clients and network resources. Network resources include hardware and/or software configured to execute server processes. Examples of network resources include a processor, a data storage, a virtual machine, a container, and/or a software application. Network resources are shared amongst multiple clients. Clients request computing services from a computer network independently of each other. Network resources are dynamically assigned to the requests and/or clients on an on-demand basis. Network resources assigned to each request and/or client may be scaled up or down based on, for example, (a) the computing services requested by a particular client, (b) the aggregated computing services requested by a particular tenant, and/or (c) the aggregated computing services requested of the computer network. Such a computer network may be referred to as a “cloud network.”
In one or more embodiments, a service provider provides a cloud network to one or more end users. Various service models may be implemented by the cloud network, including but not limited to Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS). In SaaS, a service provider provides end users the capability to use the service provider's applications, which are executing on the network resources. In PaaS, the service provider provides end users the capability to deploy custom applications onto the network resources. The custom applications may be created using programming languages, libraries, services, and tools supported by the service provider. In IaaS, the service provider provides end users the capability to provision processing, storage, networks, and other fundamental computing resources provided by the network resources. Any arbitrary applications, including an operating system, may be deployed on the network resources.
A computer network may implement various deployment, including but not limited to a private cloud, a public cloud, and/or a hybrid cloud. In a private cloud, network resources are provisioned for exclusive use by a particular group of one or more entities (the term “entity” as used herein refers to a corporation, organization, person, or other entity). The network resources may be local to and/or remote from the premises of the particular group of entities. In a public cloud, cloud resources are provisioned for multiple entities that are independent from each other (also referred to as “tenants” or “customers”). The computer network and the network resources thereof may be accessed by clients corresponding to different tenants. Such a computer network may be referred to as a “multi-tenant computer network.” Several tenants may use a same particular network resource at different times and/or at the same time. The network resources may be local to and/or remote from the premises of the tenants. In a hybrid cloud, a computer network comprises a private cloud and a public cloud. An interface between the private cloud and the public cloud allows for data and application portability. Data stored at the private cloud and data stored at the public cloud may be exchanged through the interface. Applications implemented at the private cloud and applications implemented at the public cloud may have dependencies on each other. A call from an application at the private cloud to an application at the public cloud (and vice versa) may be executed through the interface.
In one or more embodiments, tenants of a multi-tenant computer network are independent of each other. For example, a business or operation of one tenant may be separate from a business or operation of another tenant. Different tenants may demand different network requirements for the computer network. Examples of network requirements include processing speed, amount of data storage, security requirements, performance requirements, throughput requirements, latency requirements, resiliency requirements, Quality of Service (QoS) requirements, tenant isolation, and/or consistency. The same computer network may need to implement different network requirements demanded by different tenants.
In a multi-tenant computer network, tenant isolation may be implemented to ensure that the applications and/or data of different tenants are not shared with each other. Various tenant isolation approaches may be used. Each tenant may be associated with a tenant identifier (ID). Each network resource of the multi-tenant computer network may be tagged with a tenant ID. A tenant may be permitted access to a particular network resource only if the tenant and the particular network resources are associated with the same tenant ID.
For example, each application implemented by the computer network may be tagged with a tenant ID, and tenant may be permitted access to a particular application only if the tenant and the particular application are associated with a same tenant ID. Each data structure and/or dataset stored by the computer network may be tagged with a tenant ID, and tenant may be permitted access to a particular data structure and/or dataset only if the tenant and the particular data structure and/or dataset are associated with a same tenant ID. Each database implemented by the computer network may be tagged with a tenant ID, and tenant may be permitted access to data of a particular database only if the tenant and the particular database are associated with the same tenant ID. Each entry in a database implemented by a multi-tenant computer network may be tagged with a tenant ID, and a tenant may be permitted access to a particular entry only if the tenant and the particular entry are associated with the same tenant ID. However, the database may be shared by multiple tenants.
In one or more embodiments, a subscription list indicates which tenants have authorization to access which network resources. For each network resource, a list of tenant IDs of tenants authorized to access the network resource may be stored. A tenant may be permitted access to a particular network resource only if the tenant ID of the tenant is included in the subscription list corresponding to the particular network resource.
In one or more embodiments, network resources (such as digital devices, virtual machines, application instances, and threads) corresponding to different tenants are isolated to tenant-specific overlay networks maintained by the multi-tenant computer network. As an example, packets from any source device in a tenant overlay network may be transmitted only to other devices within the same tenant overlay network. Encapsulation tunnels may be used to prohibit any transmissions from a source device on a tenant overlay network to devices in other tenant overlay networks. Specifically, packets received from the source device may be encapsulated within an outer packet. The outer packet is transmitted from a first encapsulation tunnel endpoint (in communication with the source device in the tenant overlay network) to a second encapsulation tunnel endpoint (in communication with the destination device in the tenant overlay network). The second encapsulation tunnel endpoint decapsulates the outer packet to obtain the original packet transmitted by the source device. The original packet is transmitted from the second encapsulation tunnel endpoint to the destination device in the same particular overlay network.

7. Hardware Overview

In one or more embodiments, techniques described herein are implemented by one or more special-purpose computing devices. The special-purpose computing device(s) may be hard-wired to perform the techniques, and/or may include digital electronic devices such as one or more application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or network processing units (NPUs) that are persistently programmed to perform the techniques, or may include one or more general purpose hardware processors programmed to perform the techniques pursuant to program instructions in firmware, memory, other storage, or a combination thereof. Such special-purpose computing devices may also combine custom hard-wired logic, ASICs, FPGAs, or NPUs with custom programming to accomplish the techniques. A special-purpose computing device may be desktop computer systems, portable computer systems, handheld devices, networking devices, or any other device that incorporates hard-wired and/or program logic to implement the techniques.
For example, FIG. 8 is a block diagram that illustrates a computer system 800 upon which one or more embodiments of the invention may be implemented. The computer system 800 includes a bus 802 or other communication mechanism for communicating information, and a hardware processor 804 coupled with bus 802 for processing information. The hardware processor 804 may be, for example, a general-purpose microprocessor.
The computer system 800 also includes a main memory 806, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 802 for storing information and instructions to be executed by processor 804. The main memory 806 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 804. Such instructions, when stored in non-transitory storage media accessible to the processor 804, render the computer system 800 into a special-purpose machine that is customized to perform the operations specified in the instructions.
The computer system 800 further includes a read only memory (ROM) 808 or other static storage device coupled to the bus 802 for storing static information and instructions for the processor 804. A storage device 810, such as a magnetic disk or optical disk, is provided and coupled to the bus 802 for storing information and instructions.
The computer system 800 may be coupled via the bus 802 to a display 812, such as a cathode ray tube (CRT), for displaying information to a computer user. An input device 814, including alphanumeric and other keys, is coupled to the bus 802 for communicating information and command selections to the processor 804. Another type of user input device is cursor control 816, such as a mouse, a trackball, or cursor direction keys for communicating direction information and command selections to the processor 804 and for controlling cursor movement on the display 812. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
The computer system 800 may implement techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware, and/or program logic which in combination with the computer system 800 causes or programs the computer system 800 to be a special-purpose machine. In one or more embodiments, the techniques herein are performed by the computer system 800 in response to the processor 804 executing one or more sequences of one or more instructions contained in the main memory 806. Such instructions may be read into the main memory 806 from another storage medium, such as the storage device 810. Execution of the sequences of instructions contained in the main memory 806 causes the processor 804 to perform the process steps described herein. Alternatively, hard-wired circuitry may be used in place of or in combination with software instructions.
The term “storage media” as used herein refers to any non-transitory media that store data and/or instructions that cause a machine to operate in a specific fashion. Such storage media may include non-volatile media and/or volatile media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 810. Volatile media includes dynamic memory, such as the main memory 806. Common forms of storage media include, for example, a floppy disk, a flexible disk, hard disk, solid state drive, magnetic tape, or any other magnetic data storage medium, a read-only compact disc (CD-ROM), any other optical data storage medium, any physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip or cartridge, content-addressable memory (CAM), and ternary content-addressable memory (TCAM).
Storage media is distinct from but may be used in conjunction with transmission media. Transmission media participates in transferring information between storage media. For example, transmission media includes coaxial cables, copper wire and fiber optics, including the wires of the bus 802. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared data communications.
Various forms of media may be involved in carrying one or more sequences of one or more instructions to the processor 804 for execution. For example, the instructions may initially be carried on a magnetic disk or solid-state drive of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line or other communications medium, using a modem. A modem local to the computer system 800 can receive the data on the telephone line or other communications medium and use an infrared transmitter to convert the data to an infrared signal. An infrared detector can receive the data carried in the infrared signal and appropriate circuitry can place the data on the bus 802. The bus 802 carries the data to the main memory 806, from which the processor 804 retrieves and executes the instructions. The instructions received by the main memory 806 may optionally be stored on the storage device 810, either before or after execution by processor 804.
The computer system 800 also includes a communication interface 818 coupled to the bus 802. The communication interface 818 provides a two-way data communication coupling to a network link 820 that is connected to a local network 822. For example, the communication interface 818 may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface 818 may be a local area network (LAN) card configured to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface 818 sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.
The network link 820 typically provides data communication through one or more networks to other data devices. For example, the network link 820 may provide a connection through a local network 822 to a host computer 824 or to data equipment operated by an Internet Service Provider (ISP) 826. The ISP 826 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the “Internet” 828. The local network 822 and Internet 828 both use electrical, electromagnetic, or optical signals that carry digital data streams. The signals through the various networks and the signals on the network link 820 and through the communication interface 818, which carry the digital data to and from the computer system 800, are example forms of transmission media.
The computer system 800 can send messages and receive data, including program code, through the network(s), network link 820, and communication interface 818. In the Internet example, a server 830 might transmit a requested code for an application program through the Internet 828, ISP 826, local network 822, and communication interface 818.
The received code may be executed by processor 804 as it is received, and/or may be stored in the storage device 810 or other non-volatile storage for later execution.

8. Miscellaneous; Extensions

Embodiments are directed to a system with one or more devices that include a hardware processor and that are configured to perform any of the operations described herein and/or recited in any of the claims below.
In one or more embodiments, a non-transitory computer-readable storage medium stores instructions which, when executed by one or more hardware processors, cause performance of any of the operations described herein and/or recited in any of the claims.
Any combination of the features and functionalities described herein may be used in accordance with one or more embodiments. In the foregoing specification, embodiments have been described with reference to numerous specific details that may vary from implementation to implementation. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The sole and exclusive indicator of the scope of the invention, and what is intended by the applicants to be the scope of the invention, is the literal and equivalent scope of the set of claims that issue from this application, in the specific form in which such claims issue, including any subsequent correction.

Claims

What is claimed is:

1. One or more non-transitory machine-readable media storing instructions that, when executed by one or more processors, cause performance of operations comprising:

opening, in a runtime environment configured to use a garbage collector to manage memory in a heap, a memory session,

allocating a first subset of a set of foreign memory to a first memory segment associated with the memory session, the foreign memory comprising off-heap memory that is not managed by the garbage collector;

encountering, in the runtime environment, an instruction to close the memory session;

responsive to encountering the instruction to close the memory session, deallocating the first subset of the set of foreign memory.

2. The one or more non-transitory machine-readable media of claim 1, wherein opening the memory session comprises:

registering the memory session against a cleaner that is configured to (a) determine when the memory session no longer in use and (b) responsive to determining that the memory session is no longer in use, close the memory session.

3. The one or more non-transitory machine-readable media of claim 2, wherein registering the memory session against the cleaner is performed responsive to encountering an instruction to open the memory session with implicit closure.

4. The one or more non-transitory machine-readable media of claim 1, the operations further comprising:

allocating a second subset of the set of foreign memory to a second memory segment associated with the memory session;

responsive to encountering the instruction to close the memory session, further deallocating the second subset of the set of foreign memory.

5. The one or more non-transitory machine-readable media of claim 1, wherein the foreign memory comprises one or more function pointers native to an operating environment that hosts the runtime environment.

6. The one or more non-transitory machine-readable media of claim 1, wherein the memory session is confined to a particular thread.

7. The one or more non-transitory machine-readable media of claim 1, wherein the memory session is shared by a plurality of threads.

8. A system comprising:

at least one device comprising one or more hardware processors, the system being configured to perform operations comprising:

9. The system of claim 8, wherein opening the memory session comprises:

registering the memory session against a cleaner that is configured to (a) determine when the memory session is no longer in use and (b) responsive to determining that the memory session is no longer in use, close the memory session.

10. The system of claim 9, wherein registering the memory session against the cleaner is performed responsive to encountering an instruction to open the memory session with implicit closure.

11. The system of claim 8, the operations further comprising:

12. The system of claim 8, wherein the foreign memory comprises one or more function pointers native to an operating environment that hosts the runtime environment.

13. The system of claim 8, wherein the memory session is confined to a particular thread.

14. The system of claim 8, wherein the memory session is shared by a plurality of threads.

15. A method comprising:

responsive to encountering the instruction to close the memory session, deallocating the first subset of the set of foreign memory,

wherein the method is performed by at least device comprising one or more hardware processors.

16. The method of claim 15, wherein opening the memory session comprises:

17. The method of claim 16, wherein registering the memory session against the cleaner is performed responsive to encountering an instruction to open the memory session with implicit closure.

18. The method of claim 15, further comprising:

19. The method of claim 15, wherein the foreign memory comprises one or more function pointers native to an operating environment that hosts the runtime environment.

20. The method of claim 15, wherein the memory session is one of (a) confined to a particular thread, or (b) shared by a plurality of threads.