Thread (71 messages) 71 messages, 10 authors, 2012-09-04

Re: [PATCH V2 09/12] net/eipoib: Add main driver functionality

flat view

From: Or Gerlitz <hidden>
Date: 2012-08-12 13:21:00

On 12/08/2012 13:54, Michael S. Tsirkin wrote:
On Wed, Aug 08, 2012 at 08:23:15AM +0300, Or Gerlitz wrote:
quoted
quoted
So far the things that make sense. Here are some that don't, to me:
- Is a pdf presentation all you have in terms of documentation?
   We are talking communication protocols here - I would expect a
   proper spec, and some effort to standardize, otherwise where's the
   guarantee it won't change in an incompatible way?
To be precise, the solution uses 100% IPoIB wire-protocol, so we don't
see a need for any spec change / standardization effort.
Thinking about it some more, the solution is not really 100% local:
- ARP packets used at migration are visible on the network
The ARP packets on the wire are IPoIB ARP packets -- indeed, when the guest moves, the IPoIB
link layer address which was associated with the VIF that used to serve this guest on the host
we migrated from, changes to be of a VIF on the host that we migrated to.

- QPN/LID in MAC are guest visible, and could be exported on the network
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help