[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5027BA17.6010503@mellanox.com>
Date: Sun, 12 Aug 2012 17:13:43 +0300
From: Or Gerlitz <ogerlitz@...lanox.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>, <davem@...emloft.net>,
<roland@...nel.org>, <netdev@...r.kernel.org>, <ali@...lanox.com>,
<sean.hefty@...el.com>, Erez Shitrit <erezsh@...lanox.co.il>,
Doug Ledford <dledford@...hat.com>
Subject: Re: [PATCH V2 09/12] net/eipoib: Add main driver functionality
On 12/08/2012 16:55, Michael S. Tsirkin wrote:
> I didn't realize you do ARP snooping. Why? I know you mangle outgoing
> ARP packets,
Maybe I wasn't accurate/clear, we do mangle outgoing/incoming ARP
packets, from/to Ethernet ARPs
to/from IPoIB ARPs.
> this will go away if you maintain a mapping in SM accessible to all
> guests.
guests don't interact with IB, I assume you referred to dom0 code, eIPoIB or
another driver in the host. But what mapping exactly? and remember that
this code (VM through eipoib) can talk to any IPoIB element on the
fabric, native,
virtualized, HW/SW gateways, etc etc.
Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists