[openib-general] Re: We are ready with a Gen2 version of MVAPICH2

[Dhabaleswar Panda]

Hi Roland, 

>     Dhabaleswar> What I am talking about here is the new mvapich2-gen2
>     Dhabaleswar> (MPI-2) version we have developed. The existing one
>     Dhabaleswar> at the SVN is the mvapich-gen2 (MPI-1) version. Thus,
>     Dhabaleswar> we will have two directories there (one for MPI-1
>     Dhabaleswar> version and the other one for MPI-2 version).
> 
> Sorry for the confusion -- I missed the 2nd "2" in the directory
> name.  Yes, that is definitely fine.

Thanks.

>     Dhabaleswar> Thanks for reiterating the comments. I completely
>     Dhabaleswar> agree with it. As indicated above, for the existing
>     Dhabaleswar> mvapich-gen2 (MPI-1) version, we have been using the
>     Dhabaleswar> SVN repository as the real source code control system
>     Dhabaleswar> (not as the distribution channel) and we plan to
>     Dhabaleswar> continue this trend. We plan to do the same with the
>     Dhabaleswar> new mvapich2-gen2 (MPI-2) version with the SVN
>     Dhabaleswar> repository too.
> 
> Hmm... the full diffstat of all the changes to mpid made since the
> initial checkin is:
> 
> $ svn diff -r3157 mpi/mvapich-gen2/mpid/ch_gen2|diffstat -p2
>  mpid/ch_gen2/dreg.c          |    1
>  mpid/ch_gen2/ibverbs_const.h |    1
>  mpid/ch_gen2/vbuf.h          |    2 -
>  mpid/ch_gen2/viainit.c       |   51 +++++++++++++++++++++++++++++++++++++------
>  mpid/ch_gen2/viaparam.c      |   11 ++++++++-
>  mpid/ch_gen2/viaparam.h      |    1
>  6 files changed, 57 insertions(+), 10 deletions(-)
> 
> Is that really all the MPI-1 development you've done since August '05?
> (There are also some big changes like deleting most of the extra files
> and renaming a few documents, but that's all the real changes that I see)

Yes, these are all the changes done to the `gen2' version of mvapich
so far. FYI, currently, there are two different code bases for
mvapich: one for `vapi' and one for `gen2' with different version
numbers and features. They have evolved like that in the past and
currently we are working on unifying these two code bases into a
single one so that all features will be available for both vapi and
gen2 stacks. This unified code base will be available in early
February and will be updated at the OpenIB SVN.

The extra files were deleted after initial check-in because OpenIB
folks wanted a stripped down version with a smaller code size.

On the vapi-side (on the vapi code base), a lot of changes have been
happening continuously (including the latest 0.9.6 release made in
early December). However, since this code base is different and can
not work with the Gen2 stack, these changes have not been reflected on
the OpenIB SVN. After these two code bases are unified in early
February, all features/changes will be reflected on both vapi and gen2
stacks and will be reflected on the OpenIB SVN. After that you will
see frequent changes there.

On the mvpich2 side, we have taken a different approach wrt gen2. The
new mvapich2-gen2 version (which we are trying to put at the OpenIB
SVN) has the unified code base for both vapi and gen2 (i.e., all
features available on both stacks).  Thus, all future changes
(features and bug fixes) will be reflected on this unified version at
OpenIB SVN.

Hope this clarifies your questions. Let me know if you have any
additional questions.

Thanks, 

DK

>  - R.
>