[openib-general] IPoIB IETF WG presentation updated again

[Dror Goldenberg]

> -----Original Message-----
> From: Hal Rosenstock [mailto:halr at voltaire.com]
> Sent: Monday, August 02, 2004 8:36 PM
...  
> Here's another update to the IPoIB presentation (MAX_ADDR_LEN slide as
> pointed out by Tom).
 ...
> -- Hal
> 

It's good to see that MAX_ADDR_LEN has been changed to 32. Does that solve
all the IPoIB ARP related problems for 2.6 kernel ? Can we store all related
link
information in this 32 bytes ? What is envisioned to be stored in this 32
bytes - is
it just the QPN+GID, or the entire path info, or the address vector object
too ?

I think that ideally, if a network device can replace the ARP functionality
in the kernel
that'll be better. Because this way the IPoIB can get an address resolution
request 
from the IP stack, handle it by sending an ARP, then SA query for the path
record, then
creation of HCA address handle, and then place it in cache and pass back
this address
handle. When cache is replaced or expires, IPoIB will destroy the HCA
address handle.
If this is not supported, then IPoIB will still need to maintain a shadow
table.

Beyond that, it'll be nice if we could have gotten the IP datagram without
the "Ethernet"
header. Currently the IPoIB driver has to chop it, and replace it with the
IPoIB encapsulation
header. Anyway, this is just the purity of the protocol  stack layering.

Dror
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20040802/1e37c118/attachment.html>