Presentation is loading. Please wait.

Presentation is loading. Please wait.

Center for Computation & Louisiana State University - ParalleX / XPI Specification - The XPI.

Published byHayley Lavis Modified over 9 years ago

Similar presentations

Presentation on theme: "Center for Computation & Louisiana State University - ParalleX / XPI Specification - The XPI."— Presentation transcript:

1 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu The XPI Interface

2 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Early thoughts on the XPI Representation Will be updated/changed frequently

3 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Goals Provide Programming Execution Model Functionality: ParalleX / HPX Speed: Incur minimal overhead Interface: Similar to MPI when possible Small: minimal set of functions and objects

4 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Things We Rely on Being Fast Remote Direct Memory Addressing Light Weight Threads Active Messages (Parcels) Atomic Memory Operations Work Queues

5 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu LCO Constructor – In: receptor, byte_array get_gid – Out: GID free

6 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu LCO waitany # listen to multiple lco's counted_waitany # listen to multiple lco's

7 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu LCO write # possibly remote operation – In: byte_array – In: Offset – In: Len wait # local, returns when a write occurs – In: Timeout – Out: return code: error, interrupt, success, etc. counted_wait # local, return when number of writes is # greater than the number of # counted waits – In: Timeout

8 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Complex/Thread: LCO Complex/Thread constructor – In: Action – In: data, byte_array – In: receptor, byte_array # can be null – Optional In: contin1, (T) Thread, (TL) Thread_list – Optional In: contin2, (G) GID, (GL) GID_list start – Optional Out: (R) RunningThread set_state get_state

9 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Complex send_and_exit – In: byte_array – In: Offset – In: Length – # This writes to all continuations # and terminates the thread

10 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Pseudo C Code XPI_Action action; XPI_Thread thread, next1, next2; XPI_RunningThread run; XPI_GID gid; struct BH_data *bh_data; XPI_Buffer_init(sizeof(BH_data),XPI_RECEIVE,&bh_data);... XPI_Thread_init_T(&thread,&action,bh_data,&next); XPI_Thread_start_R(&thread,&run); XPI_Thread_getgid(&thread,&gid);.... XPI_RunningThread_set_state(&run,XPI_TERMINATE);

11 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Action: Portable Function Ref Action constructor – In: function_id, String – In: data_size, int – In: data_repacker, Action Name of function used to repackage bytes for use on possibly different architectures available on a machine. Potentially difficult to write, auto generated by XPIPP tool based in on interface definition language. Null used on machines with homogeneous architecture.

12 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Memory Managment mem_alloc – In: size, int – In: flags, int RECEIVE: can be a target for RDMA – In: data_repacker, Action # special value: IMMOBILE # special value: ARRAY_OF_INT # rely on tools to generate repackers – Out: ref, (P) byte_array, (G) GID

13 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Memory Management mem_free – In: data, (P) byte_array, (G) GID mem_getptr – In: GID – Out: byte_array mem_getgid, – In: byte_array – out: GID Use this to unify disk and memory access as Jack Dennis suggests?

14 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Pseudo C Code // Data managed by XPI void init_data(void *intrinsic,void *recvd) { struct BH_data *bh_data = (struct BH_data *)intrinsic;... BH_event_horizon *eh; XPI_Buffer_init(sizeof(eh),flags,&eh); XPI_send_and_exit(eh); // received by continuations } XPI_Action action; XPI_Action_init(&action,"black_hole.init_data",10,NULL);

15 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu WorkQueue: LCO WorkQueue constructor – Out: id, (R) GID – In: receptor, byte_array # WorkQueue runs one thread at a time. All threads share # the receptor as the second argument to the action add: – In: Complex/Thread # called if the GID is a parcel target

16 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Parcels Parcel constructor: – In: Action – In: Data – In: destination, GID – Optional In: contin, (G) GID, (GL) GID_list start

17 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Locality static Locality get_locality() – get_gid: Out: GID – get_property: In: name, String Out: value, int

18 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Process Process constructor – In: parent, GID – In: Locality_List set_policy: In: policy, In: param get_policy: In: policy, Out: param get_gid: Out: GID

19 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Process bind_symname – In: sym_name, String # e.g. "console" – In: GID unbind_symname – In: sym_name, String get_main: static: Out: GID get_parent: Out: GID, In: GID – all GID's have a parent process! get_current: static: Out: GID

20 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Parcels Semantically similar to Thread A better way to start a thread: Destination can be a process, that starts a thread at the least loaded of the managed localities

21 Center for Computation & Technology @ Louisiana State University - http://cct.lsu.edu/ ParalleX / XPI Specification - http://parallex.cct.lsu.edu Mobile Objects (AGAS) WorkQueue (easy) Suspended Thread (difficult) Just move work queues to start?

Download ppt "Center for Computation & Louisiana State University - ParalleX / XPI Specification - The XPI."

Similar presentations

Categories of I/O Devices

Categories of I/O Devices
MPI Message Passing Interface

MPI Message Passing Interface
R4 Dynamically loading processes. Overview R4 is closely related to R3, much of what you have written for R3 applies to R4 In R3, we executed procedures.

R4 Dynamically loading processes. Overview R4 is closely related to R3, much of what you have written for R3 applies to R4 In R3, we executed procedures.
CS 450 Module R4. R4 Overview Due on March 11 th along with R3. R4 is a small yet critical part of the MPX system. In this module, you will add the functionality.

CS 450 Module R4. R4 Overview Due on March 11 th along with R3. R4 is a small yet critical part of the MPX system. In this module, you will add the functionality.
Module R2 Overview. Process queues As processes enter the system and transition from state to state, they are stored queues. There may be many different.

Module R2 Overview. Process queues As processes enter the system and transition from state to state, they are stored queues. There may be many different.
Module R2 CS450. Next Week R1 is due next Friday ▫Bring manuals in a binder - make sure to have a cover page with group number, module, and date. You.

Module R2 CS450. Next Week R1 is due next Friday ▫Bring manuals in a binder - make sure to have a cover page with group number, module, and date. You.
Process Synchronization. Module 6: Process Synchronization Background The Critical-Section Problem Peterson’s Solution Synchronization Hardware Semaphores.

Process Synchronization. Module 6: Process Synchronization Background The Critical-Section Problem Peterson’s Solution Synchronization Hardware Semaphores.
1 CMSC421: Principles of Operating Systems Nilanjan Banerjee Principles of Operating Systems Assistant Professor, University of Maryland Baltimore County.

1 CMSC421: Principles of Operating Systems Nilanjan Banerjee Principles of Operating Systems Assistant Professor, University of Maryland Baltimore County.
Tam Vu (tvu@mail.eecis.udel.edu) Remote Procedure Call CISC 879 – Spring 03 Tam Vu (tvu@mail.eecis.udel.edu) March 06, 03.

Tam Vu Remote Procedure Call CISC 879 – Spring 03 Tam Vu March 06, 03.
Implementing Remote Procedure Calls Authors: Andrew D. Birrell and Bruce Jay Nelson Xerox Palo Alto Research Center Presenter: Jim Santmyer Thanks to:

Implementing Remote Procedure Calls Authors: Andrew D. Birrell and Bruce Jay Nelson Xerox Palo Alto Research Center Presenter: Jim Santmyer Thanks to:
3/17/2008Prof. Hilfinger CS 164 Lecture 231 Run-time organization Lecture 23.

3/17/2008Prof. Hilfinger CS 164 Lecture 231 Run-time organization Lecture 23.
Processes 1 CS502 Spring 2006 Processes Week 2 – CS 502.

Processes 1 CS502 Spring 2006 Processes Week 2 – CS 502.
11/11/05ELEC6200-0011 CISC (Complex Instruction Set Computer) Veeraraghavan Ramamurthy ELEC 6200 Computer Architecture and Design Fall 2005.

11/11/05ELEC CISC (Complex Instruction Set Computer) Veeraraghavan Ramamurthy ELEC 6200 Computer Architecture and Design Fall 2005.
CSE 451 Section 4 Project 2 Design Considerations.

CSE 451 Section 4 Project 2 Design Considerations.
1.3 Executing Programs. How is Computer Code Transformed into an Executable? Interpreters Compilers Hybrid systems.

1.3 Executing Programs. How is Computer Code Transformed into an Executable? Interpreters Compilers Hybrid systems.
1.11 Introduction to OOP academy.zariba.com 1. Lecture Content 1.What is OOP and why use it? 2.Classes and objects 3.Static classes 4.Properties, fields.

1.11 Introduction to OOP academy.zariba.com 1. Lecture Content 1.What is OOP and why use it? 2.Classes and objects 3.Static classes 4.Properties, fields.
ADLB Update Recent and Current Adventures with the Asynchronous Dynamic Load Balancing Library Rusty Lusk Mathematics and Computer Science Division Argonne.

ADLB Update Recent and Current Adventures with the Asynchronous Dynamic Load Balancing Library Rusty Lusk Mathematics and Computer Science Division Argonne.
UNIX System Administration OS Kernal Copyright 2002, Dr. Ken Hoganson All rights reserved. OS Kernel Concept Kernel or MicroKernel Concept: An OS architecture-design.

UNIX System Administration OS Kernal Copyright 2002, Dr. Ken Hoganson All rights reserved. OS Kernel Concept Kernel or MicroKernel Concept: An OS architecture-design.
Introduction to Processes CS 537 - Intoduction to Operating Systems.

Introduction to Processes CS Intoduction to Operating Systems.
LWIP TCP/IP Stack 김백규.

LWIP TCP/IP Stack 김백규.

Similar presentations

Ads by Google