System and method to provide explicit multicast local identifier assignment for per-partition default multicast local identifiers defined as subnet manager policy input in a high performance computing environment
US-2018309587-A1 · Oct 25, 2018 · US
US11405229B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11405229-B2 |
| Application number | US-202017121410-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 14, 2020 |
| Priority date | Mar 24, 2017 |
| Publication date | Aug 2, 2022 |
| Grant date | Aug 2, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for providing explicit multicast local identifier assignment for per-partition default multicast local identifiers defined as subnet manager policy input in a high performance computing environment. In accordance with an embodiment, an explicit multicast local identifier (MLID) assignment policy can be provided (as, e.g., administrative input) that explicitly defines which MLIDs will be used for which partitions in a subnet. Further, an MLID assignment policy can also define which dedicated MLIDs will be associated with given multicast group identifiers (for example, partition independent MLIDs). By employing such an MLID assignment policy, a new or restarted master subnet manger can observe and verify the MLIDs used for existing partitions, instead of generating new MGID to MLID mappings. In this way, changes in MLID associations for any corresponding MGID can be avoided as a result of master SM restarts or failovers, or any subnet-merge operations.
Opening claim text (preview).
What is claimed is: 1. A method for supporting explicit multicast local identifier assignment for per-partition default multicast local identifiers defined as subnet manager policy input in a high performance computing environment, the method comprising: providing, to an operational management entity of a subnet, a default multicast local identifier (MLID) included in the subnet manager policy input, the default MLID being assigned, by a processor of the high performance computing environment, to a partition of a plurality of partitions defined within the subnet based on the subnet manager policy input; creating a mapping between the default MLID and the partition; storing the mapping in a memory accessible by the operational management entity; shutting down the operational management entity of the subnet; providing the default MLID to a new operational management entity of the subnet; and upon the default MLID being provided to the new operational management entity, assigning, by the new operational management entity, the default MLID to the partition defined within the subnet by accessing the accessible memory. 2. The method of claim 1 , wherein the operational management entity is shut down as a result of a restart of the subnet. 3. The method of claim 2 , wherein new operational management entity of the subnet comprises a restarted operational management entity of the subnet. 4. The method of claim 3 , wherein the assigning, by the new operational management entity, the default MLID to the partition of the plurality of partitions defined within the subnet comprises: determining, by the new operational management entity, the mapping between the default MLID and the partition comprising the accessing the accessible memory, and re-initializing, by the new operational subnet manager, the subnet, wherein upon re-initialization of the subnet, the default MLID is assigned to the partition of the plurality of partitions. 5. The method of claim 1 , wherein the default MLID is within a defined range of a plurality of MLIDs. 6. The method of claim 5 , wherein the defined range of the plurality of MLIDs comprises a range of MLIDs defined by a starting MLID and an ending MLID. 7. The method of claim 6 , wherein the operational subnet manager sets the starting MLID and the ending MLID as a result of receiving instructions indicative of the starting MLID and the ending MLID. 8. A system for supporting explicit multicast local identifier assignment for per-partition default multicast local identifiers defined as subnet manager policy input in a high performance computing environment, the system comprising: an operational management entity of a subnet, wherein a default multicast local identifier (MLID), included in the subnet manager policy input, is provided, by a processor of the high performance computing environment, to the operational management entity, the default MLID being assigned to a partition of a plurality of partitions defined within the subnet based on the subnet manager policy input; wherein a mapping between the default MLID and the partition is created; wherein the mapping is stored in a memory accessible by the operational management entity; wherein the operational management entity of the subnet is shut down; wherein the default MLID is provided to a new operational management entity of the subnet; and wherein upon the default MLID being provided to the new operational management entity, the default MLID is assigned, by the new operational management entity, to the partition defined within the subnet by accessing the accessible memory. 9. The system of claim 8 , wherein the operational management entity is shut down as a result of a restart of the subnet. 10. The system of claim 9 , wherein new operational management entity of the subnet comprises a restarted operational management entity of the subnet. 11. The system of claim 10 , wherein the assigning, by the new operational management entity, the default MLID to the partition of the plurality of partitions defined within the subnet comprises: determining, by the new operational management entity, the mapping between the default MLID and the partition comprising the accessing the accessible memory, and re-initializing, by the new operational subnet manager, the subnet, wherein upon re-initialization of the subnet, the default MLID is assigned to the partition of the plurality of partitions. 12. The system of claim 8 , wherein the default MLID is within a defined range of a plurality of MLIDs. 13. The system of claim 12 , wherein the defined range of the plurality of MLIDs comprises a range of MLIDs defined by a starting MLID and an ending MLID. 14. The system of claim 13 , wherein the operational subnet manager sets the starting MLID and the ending MLID as a result of receiving instructions indicative of the starting MLID and the ending MLID. 15. A non-transitory computer readable storage medium having instructions thereon for supporting explicit multicast local identifier assignment for per-partition default multicast local identifiers defined as subnet manager policy input in a high performance computing environment, which when read and executed by cause a computer to perform steps comprising: providing, to an operational management entity of a subnet, a default multicast local identifier (MLID) included in the subnet manager policy input, the default MLID being assigned, by a processor of the high performance computing environment, to a partition of a plurality of partitions defined within the subnet based on the subnet manager policy input; creating a mapping between the default MLID and the partition; storing the mapping in a memory accessible by the operational management entity; shutting down the operational management entity of the subnet; providing the default MLID to a new operational management entity of the subnet; and upon the default MLID being provided to the new operational management entity, assigning, by the new operational management entity, the default MLID to the partition defined within the subnet by accessing the accessible memory. 16. The non-transitory computer readable storage medium of claim 15 , wherein the operational management entity is shut down as a result of a restart of the subnet. 17. The non-transitory computer readable storage medium of claim 16 , wherein new operational management entity of the subnet comprises a restarted operational management entity of the subnet. 18. The non-transitory computer readable storage medium of claim 17 , wherein the assigning, by the new operational management entity, the default MLID to the partition of the plurality of partitions defined within the subnet comprises: determining, by the new operational management entity, the mapping between the default MLID and the partition comprising the accessing the accessible memory, and re-initializing, by the new operational subnet manager, the subnet, wherein upon re-initialization of the subnet, the default MLID is assigned to the partition of the plurality of partitions. 19. The non-transitory computer readable storage medium of claim 15 , wherein the default MLID is within a defined range of a plurality of MLIDs. 20. The non-transitory computer readable storage medium of claim 19 , wherein the defined range of the plurality of MLIDs comprises a range of MLIDs defined by a starting MLID and an ending MLID.
broadcast or multicast in a specific location, e.g. geocast (protocols for adapting network applications to user terminal location H04L67/52; services specially adapted for wireless communication networks making use of the location of users or terminals H04W4/02) · CPC title
with management of multicast group membership · CPC title
with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains · CPC title
wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30) · CPC title
Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.