The MVAPICH team is pleased to announce the release of MVAPICH2-1.7
and OSU Micro-Benchmarks (OMB) 3.4.
The complete set of Features, Enhancements, and Bug Fixes for MVAPICH2
1.7 (since MVAPICH2-1.6 release) are listed here.
- Based on MPICH2-1.4.1p1
- Integrated Hybrid (UD-RC/XRC) design
> I wonder how important wire compatibilty of the ibv_xx_pingpong
> examples is... should I worry about this?
I know that for some of the larger clusters, they may not be able to upgrade
the software on all systems during a scheduled downtime. This is about the
only reason I can think of why yo
- Original Message -
> On Wed, Oct 12, 2011 at 9:32 AM, Wendy Cheng
> wrote:
> > The OFED package itself does include XRC support. The issue here
> > (my
> > guess) is that its build script needs to understand the running
> > system's kernel version to decide what should be pulled (from th
- Original Message -
> On Tue, Oct 11, 2011 at 7:39 PM, Jason Gunthorpe
> wrote:
> > On Tue, Oct 11, 2011 at 09:02:41AM -0500, Christoph Lameter wrote:
> >> Has XRC support not been merged? How can I build the OFED
> >> libraries
> >> against Linux 3.1? I'd really like to get rid of the OF
- Original Message -
> On Thu, Oct 13, 2011 at 10:24 AM, Christoph Lameter
> wrote:
> >> Clean reviewed patches for this are where?
> >
> > They are in OFED-1.5.3.1 so they were already released.
>
> OFED is neither clean nor reviewed. Really. The stuff in OFED
> always
> needs a bunch
On Thu, Oct 13, 2011 at 9:12 AM, Steve Wise wrote:
> I'm not sure other drivers have this issue. For example, when a mlx or
> mthca QP moves out of RTS, does the HW flush the pending recv WRs? For
> Chelsio devices, the provider driver/library must handle this.
Yeah, mthca will generate the flu
> I pulled the xrc patches in your for-next branch and ran some simple
> tests against it. Between the last time I tested XRC and now, I'm now
> seeing mvapich2 hang during MPI finalize, which I'm debugging.
Just an update: the issues that I was seeing were caused by missing patches in
my librar
On Fri, Oct 14, 2011 at 8:54 AM, Vipul Pandya wrote:
> 1) We make our patch series against 'linux-next' tree (which has
> ‘drivers/net’ directory changes and latest changes from ‘infiniband’ tree)
> and submit them to you and you can accordingly decide when to merge them in
> your tree.
This seem
On Fri, Oct 14, 2011 at 9:36 AM, Hefty, Sean wrote:
> Actually, mine did too. I wonder if this OFED patch to libibverbs is causing
> the issue:
>
> http://git.openfabrics.org/git?p=ofed_1_5/libibverbs.git;a=blob;f=fixes/rocee_examples.patch;h=eda5a401a3424a104e8100848b5b6bf4e5b63bee;hb=HEAD
Hmm
> Our 3.1-rc9 included Rolands for-next branch.
Actually, mine did too. I wonder if this OFED patch to libibverbs is causing
the issue:
http://git.openfabrics.org/git?p=ofed_1_5/libibverbs.git;a=blob;f=fixes/rocee_examples.patch;h=eda5a401a3424a104e8100848b5b6bf4e5b63bee;hb=HEAD
--
To unsubscri
On Fri, Oct 14, 2011 at 9:31 AM, Christoph Lameter wrote:
> Our 3.1-rc9 included Rolands for-next branch.
There are a few RDMA-related changes there :)
A bisect from 3.1-rc9 to my for-next branch shouldn't take too long if
you get chance,
otherwise I'll try to take a look soon.
This is with mlx
On Fri, 14 Oct 2011, Hefty, Sean wrote:
> > Running ibv_ud_pingpong and ibc_uc_pingpong between two hosts. One with
> > OFED 1.5.3.1 (Ubuntu LTS 10.04) and another on linux 3.1.0-rc9 (Same
> > ubuntu version uderlying) with the upstream libraries.
>
> FWIW, I was able to run 3.1-rc9 in loopback an
> Running ibv_ud_pingpong and ibc_uc_pingpong between two hosts. One with
> OFED 1.5.3.1 (Ubuntu LTS 10.04) and another on linux 3.1.0-rc9 (Same
> ubuntu version uderlying) with the upstream libraries.
FWIW, I was able to run 3.1-rc9 in loopback and between 3.0 and 3.1-rc9
systems. I don't have
Running ibv_ud_pingpong and ibc_uc_pingpong between two hosts. One with
OFED 1.5.3.1 (Ubuntu LTS 10.04) and another on linux 3.1.0-rc9 (Same
ubuntu version uderlying) with the upstream libraries.
ibv_uc_pingpong
OFED:
# ibv_uc_pingpong
local address: LID 0x000a, QPN 0x54004d, PSN 0x00637e, GI
14 matches
Mail list logo