On Tue, 2019-05-07 at 08:03 -0500, Steve Wise wrote:
> On Mon, May 6, 2019 at 3:39 PM Doug Ledford <dledford@xxxxxxxxxx> wrote:
> > So, Jason and I were discussing the soft-iWARP driver submission, and he
> > thought it would be good to know if it even works with the various iWARP
> > hardware devices. I happen to have most of them on hand in one form or
> > another, so I set down to test it. In the process, I ran across some
> > issues just with the hardware versions themselves, let alone with soft-
> > iWARP. So, here's the results of my matrix of tests. These aren't
> > performance tests, just basic "does it work" smoke tests...
> >
> > Hardware:
> > i40iw = Intel x722
> > qed1 = QLogic FastLinQ QL45000
> > qed2 = QLogic FastLinQ QL41000
> > cxgb4 = Chelsio T520-CR
> >
> >
> >
> > Test 1:
> > rping -s -S 40 -C 20 -a $local
> > rping -c -S 40 -C 20 -I $local -a $remote
> >
> > Server Side
> > i40iw qed1 qed2 cxgb4 siw
> > i40iw FAIL[1] FAIL[1] FAIL[1] FAIL[1] FAIL[1]
> > qed1 FAIL[1] FAIL[1] FAIL[1] FAIL[1] FAIL[1]
> > qed2 FAIL[1] FAIL[1] FAIL[1] FAIL[1] FAIL[1]
> > cxgb4 FAIL[1] FAIL[1] FAIL[1] FAIL[1] FAIL[1]
> > siw FAIL[2] FAIL[1] FAIL[1] FAIL[1] Untested
> >
> > Failure 1:
> > Client side shows:
> > client DISCONNECT EVENT...
> > Server side shows:
> > server DISCONNECT EVENT...
> > wait for RDMA_READ_ADV state 10
> >
>
> Hey Doug,
>
> Try adding -Vv to display the ping data.. The log message you cite
> are normal, not indicative of an error.
You know...I had -vV on my initial test runs before I checked out the
entire matrix of machines to run this set of tests, and somehow it got
dropped. I think you're right, and all these FAILS can be marked as
PASS instead. It is certainly an awkward way to end a successful test,
but I do think it is passing.
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
Attachment:
signature.asc
Description: This is a digitally signed message part
