Data communications in a parallel active messaging interface of a parallel computer

• US 8,838,933 B2
• Filed: 11/16/2012
• Issued: 09/16/2014
• Est. Priority Date: 02/15/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Blocksome, Michael A., Ratterman, Joseph D., Smith, Brian E.
• Primary Examiner(s): MACKALL, LARRY T
• Application Number:
  US13/679,042
• Publication Number:
  US 20130097404A1
• Time in Patent Office: 669 Days
• Field of Search: 711/203, 711/206, 711/147, 711/E12.001
• US Class Current: 711/203
• CPC Class Codes: G06F 12/1036 for multiple virtual address spaces, e.g. segmentation G06F12/1045 takes precedence
• CPC Class Codes: G06F 15/17337 Direct connection machines, e.g. completely connected computers, point to point communication networks coupling between buses G06F13/4004

Abstract

Eager send data communications in a parallel active messaging interface (‘PAMI’) of a parallel computer, the PAMI composed of data communications endpoints that specify a client, a context, and a task, including receiving an eager send data communications instruction with transfer data disposed in a send buffer characterized by a read/write send buffer memory address in a read/write virtual address space of the origin endpoint; determining for the send buffer a read-only send buffer memory address in a read-only virtual address space, the read-only virtual address space shared by both the origin endpoint and the target endpoint, with all frames of physical memory mapped to pages of virtual memory in the read-only virtual address space; and communicating by the origin endpoint to the target endpoint an eager send message header that includes the read-only send buffer memory address.

Claims

1. A method of eager send data communications in a parallel active messaging interface (‘

PAMI’

) of a parallel computer, the parallel computer comprising a plurality of compute nodes that execute a parallel application, the PAMI comprising data communications endpoints, each endpoint comprising a specification of data communications parameters for a thread of execution on a compute node, including specifications of a client, a context, and a task, the compute nodes and the endpoints coupled for data communications through the PAMI and through data communications resources, the method comprising;

receiving in an origin endpoint of the PAMI an eager send data communications instruction that specifies a transmission of transfer data from the origin endpoint to a target endpoint, the transfer data disposed in a send buffer, the send buffer characterized by a read/write send buffer memory address in a read/write virtual address space of the origin endpoint;

determining by the origin endpoint for the send buffer a read-only send buffer memory address in a read-only virtual address space, the read-only virtual address space shared by both the origin endpoint and the target endpoint, the read-only virtual address space non-overlapping with respect to the read/write virtual address space, the read-only virtual address space established by an operating system of the parallel computer with all frames of physical memory mapped to pages of virtual memory in the read-only virtual address space; and

communicating by the origin endpoint to the target endpoint an eager send message header that includes the read-only send buffer memory address.

2. The method of claim 1 wherein:

the read/write virtual address space and the read-only virtual address space are both characterized by a same virtual address space size;

all frames of physical memory mapped to pages of virtual memory further comprises frames mapped to pages with memory addresses that are identical except for the most significant bit in each address; and

determining for the send buffer a read-only send buffer memory address in a read-only virtual address space comprises setting a most significant bit in the read/write send buffer memory address.

3. The method of claim 1 wherein determining for the send buffer a read-only send buffer memory address in a read-only virtual address space comprises determining for the send buffer a read-only send buffer memory address in a read-only virtual address space through a PAMI query to the operating system.

4. The method of claim 1 wherein:

the operating system maintains records of associations among addresses in physical memory, in read/write virtual address spaces, and in the read-only virtual address space; and

determining for the send buffer a read-only send buffer memory address in a read-only virtual address space further comprises finding through the operating system a physical memory address associated with the read/write send buffer memory address and a read-only virtual memory address associated with the physical memory address.

5. The method of claim 1 wherein:

each endpoint of the PAMI operates with a separate read/write virtual address space backed by real memory; and

all endpoints of the PAMI share the read-only virtual address space, the read-only virtual address space being non-overlapping with respect to all of the separate read/write virtual address spaces of the endpoints.

6. The method of claim 1 further comprising copying by the target endpoint transfer data from the send buffer to a target receive buffer that is characterized by a read/write receive buffer memory address in a read/write virtual address space of the target endpoint.

7. The method of claim 1 further comprising using by the target endpoint the send buffer as a target receive buffer without copying by the target endpoint transfer data from the send buffer to a receive buffer.

8. The method of claim 1 wherein:

each client comprises a collection of data communications resources dedicated to the exclusive use of an application-level data processing entity;

each context comprises a subset of the collection of data processing resources of a client, context functions, and a work queue of data transfer instructions to be performed by use of the subset through the context functions operated by an assigned thread of execution; and

each task represents a process of execution of the parallel application.

9. The method of claim 1 wherein each context carries out, through post and advance operations, data communications for the application on data communications resources in the exclusive possession of that context.

10. The method of claim 1 wherein each context carries out data communications operations independently and in parallel with other contexts.