The requirement is mostly driven from the receiving side. For cxgb3 it
is anyway...
Maybe you can help me understand the spec here. If we ignore this feature for a
minute, then the side that calls rdma_connect() must instead issue the first
'send' request to the server. Can the first 'send' be
From RFC 5044, section 7.1.2 Connection Startup Rules, Page 29:
4. MPA Responder mode implementations MUST receive and validate at
least one FPDU before sending any FPDUs or Markers.
Note: This requirement is present to allow the Initiator time to
get its receiver into
Here is the thread where we discussed how to implement peer-to-peer for
iWARP in Nov/2007:
http://lists.openfabrics.org/pipermail/general/2007-November/043252.html
Steve Wise wrote:
From RFC 5044, section 7.1.2 Connection Startup Rules, Page 29:
4. MPA Responder mode implementations
I'm just trying to define the scope of the issue here... so is there any
conceivable real-life situation where neither a 0B read nor a 0B write
would work, and the connection setup will have to use a 0B send?
i'm not sure what you mean by real-life. For the rnics we have:
nes -
Sean Hefty wrote:
nes - requires 0b write
cxgb3 - requires 0b read
amso1100 - won't work in p2p mode
I'm assuming by requires that you, uhm, mean requires, and nes couldn't do 0b
reads, or cxgb3 0b writes.
Well, I'm not sure about nes. But cxgb3 cannot deal with receiving a 0B
write
Caitlin Bestler wrote:
On Tue, May 6, 2008 at 11:32 AM, Steve Wise [EMAIL PROTECTED] wrote:
Roland Dreier wrote:
- always do peer2peer and don't let the app choose. This forces
the overhead of p2p mode on all apps, but preserves the API.
How bad is the overhead?
- R.
