[ofa-general] Re: NFSRDMA connectathon prelim. testing status,
Vu Pham
vuhuong at mellanox.com
Mon Feb 23 10:03:24 PST 2009
Tom,
> Vu:
>
> What memory registration model are you using?
It is 6 (when the connection/mount established)
>
> Vu Pham wrote:
>> Hi Tom,
>>
>> I have both nfsrdma client and server on 2.6.29-rc5 kernel,
>> nfs-utils-1.1.4. I'm using both Infinihost III (ib_mthca) and
>> ConnectX (mlx4_ib) HCAs
>> I have seen several problems during my testing at NFS Connectathon 2009
>>
>> 1. When I used ConnectX (mlx4_ib) HCAs on both client and server, the
>> client can not mount. Talking to Tom Talpey and scanning the code, I
>> saw that xprtrdma module is using ib_reg_phys_mr() and mlx4_ib verbs
>> provider does not have the implementation for this verb.
>> If I have client on mlx4_ib and server on ib_mthca, I hit the
>> following crash because of bad error handling in xprtrdma (see file
>> attached - mlx4_mount_problem.log)
>>
>> Because of this problem, I use InfiniHost III (ib_mthca) for all of
>> my tests at Connectathon
>>
>> 2. Testing Linux nfsrdma client against both Linux and OpenSolaris
>> nfsrdma servers, I hit the process hung problem during the
>> connectathon's lock test (seeing sync_page_1.log and sync_page_2.log
>> attached files). I can only reproduce it when I ran connectathon more
>> than 500 iterations (-N 1000)
>> I can NOT reproduce the problem with nfs client/server over IPoIB
>>
>> 3. Testing openSolaris nfsrdma client against linux nfsrdma server, I
>> hit the following BUG_ON() right away(see file attached -
>> svcrdma_send.log)
>>
>> thanks,
>> -vu
>>
>
More information about the general
mailing list