[Mpi3-hybridpm] endpoint proposal

Supalov, Alexander alexander.supalov at intel.com
Mon Oct 24 05:25:30 CDT 2011


Thanks. Has someone tried to look into #217 (helper threads) and #284 (endpoints) with the view on merging them? After all, threads attaching to the endpoints are almost, but not quite unlike helper threads given on "loan" to the MPI implementation. In the first case, the application is using the threads by itself. In the second case, the MPI is using threads for internal purposes. See the analogy? In both cases we let threads use or be used by MPI. Is this something one could possibly unite? They are being placed like on different sides of the boundary:

Endpoints (#284):

	Application threads
	Endpoints
	Communication resources

Helper threads (#217):

	[Endpoints]
	Internal threads
	Communication resources

So, if we merge the pictures:

	Application threads
	Endpoints (#284)
	Internal threads (#217)
	Communication resources

And what the unification would do is provide a way to convert the application threads into the internal threads and back. May be orthogonal, but certainly deserves a joint consideration.

-----Original Message-----
From: mpi3-hybridpm-bounces at lists.mpi-forum.org [mailto:mpi3-hybridpm-bounces at lists.mpi-forum.org] On Behalf Of Marc Snir
Sent: Thursday, October 20, 2011 10:40 PM
To: mpi3-hybridpm at lists.mpi-forum.org
Subject: [Mpi3-hybridpm] endpoint proposal

Slides and text for the endpoint proposal



--------------------------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland 
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052





More information about the mpiwg-hybridpm mailing list