A few comments about your question:

1) SDR cards can only reach about 7.7G bit of bw due to the 8:10 encoding and 
other overhead.
2) There haven't been a lot of work done on performance on the last years, but 
checksum offload and large send offload have been added (assuming that your 
card support it. Connectx is an example to a card that supports this features).
3) Using 4k MTU should allow you to reach higher bw. (again, you will need 
Connectx).
4) Since computers are much stronger today than they have been on 2007, you 
should be able to reach very close to the theoretical bw (of SDR).
5) When working with full bw cpu of the receiver will be the bottleneck.
6) Our software is being tested on windows server 2008 R2. This is one of the 
operating systems that we do whql on. We believe that it should also work for 
windows 7 64 bits, but we don't really test there.

Thanks
Tzachi


________________________________
From: [email protected] 
[mailto:[email protected]] On Behalf Of Ishaan Dalal
Sent: Monday, March 08, 2010 2:03 AM
To: [email protected]
Subject: [ofw] Current IPoIB performance with WinOF

Hi,

I'd like to experiment with IB as a cheap 10+ Gbps point-to-point interconnect 
(4x SDR adapters are available quite cheap) between a video editing workstation 
(Win 7 x64) and a storage server (Server 2008 R2). SMB will be used to maintain 
compatibility with other existing clients. The server is a fairly powerful 
machine (dual-core Core i5) with a RAID subsystem that can saturate a gigabit 
link several times over.

Digging through list archives to determine IPoIB performance in Windows, the 
latest I could find were posts from 2006-2007 that claimed performance was poor 
because the way IPoIB was implemented was extremely CPU-intensive. How much has 
IPoIB performance improved with the newer WinOF/NDIS versions? Is it still as 
tightly CPU-bound?

Thanks,
-Ishaan
_______________________________________________
ofw mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw

Reply via email to