Oracle's uDAPL ipc implementation uses 64 bytes of private connection data -
currently - some of this is the result of having 64 bytes to use at the
start - so we designed around this. We can probably reduce this somewhat.
And of course if we want to rewrite our connection handling for uDAPL (add
our own wire protocol) we can probably skip using the uDAPL connection data
all together.
For RDS we use our own connection data sent via datagrams which has always
been part of the Oracle UDP ipc implementation.
----- Original Message -----
From: "Roland Dreier" <[EMAIL PROTECTED]>
To: "James Lentini" <[EMAIL PROTECTED]>
Cc: "Richard Frank" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[email protected]>; "Davis, Arlin R" <[EMAIL PROTECTED]>
Sent: Wednesday, October 19, 2005 5:56 PM
Subject: Re: [dat-discussions] RE: [openib-general] Re: iWARP
emulationprotocol
James> The D is somewhat misleading. It refers to the
James> functionality provider to the consumer application.
Right, that's what we're talking about. The RDS implementation only
needs a few bytes of private data on top of the IP address info. So
the RDS implementation itself is clearly OK with any of the proposals
being discussed here.
However, Rick mentioned that Oracle needs 64 bytes of private data in
both directions for connections. My question was how Oracle works on
top of RDS, which does not provide any private data to consumers.
- R.
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
