The idea behind dynamic windows was to make them possible to implement today and push the vendors to support a more rational programming model tomorrow. Like Jim, I'm not sure
things are bleak enough that we should change.
In OFED, I think it would be very difficult today. But with Mellanox's work to support dynamic registration cache in hardware, I think things are trending in the right direction there.
For Portals 4, if an implementation supports the BIND_INACCESSIBLE feature, and I think most implementations will, supporting dynamic windows is straight-forward.
PAMI and DMAPP are probably more difficult, but a firehose-like setup should be possible until hardware catches up.
Brian
--
Brian W. Barrett
Scalable System Software Group
Sandia National Laboratories
From: mpiwg-rma [mpiwg-rma-bounces@lists.mpi-forum.org] on behalf of Jeff Hammond [jeff.science@gmail.com]
Sent: Sunday, December 01, 2013 10:16 AM
To: MPI WG Remote Memory Access working group
Cc: MPI WG Remote Memory Access working group
Subject: [EXTERNAL] Re: [mpiwg-rma] making dynamic windows suck less
How do you do pure (i.e. active-message and rendezvous-free) RDMA with just a virtual address (MPI_Aint) in (1) PAMI, (2) OFED, (3) DMAPP, (4) Portals4?
Jeff
Sent from my iPhone
Can the MPI_Win_memobj be an MPI_Aint?
I don't share this pessimism with respect to dynamic windows; I think we need to prove that these issues exist before we try to fix them.