lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <877gt415lu.fsf@xmission.com> Date: Sun, 12 Aug 2012 08:40:13 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Or Gerlitz <or.gerlitz@...il.com> Cc: "Michael S. Tsirkin" <mst@...hat.com>, Or Gerlitz <ogerlitz@...lanox.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 Or Gerlitz <or.gerlitz@...il.com> writes: > On Sun, Aug 5, 2012 at 9:50 PM, Michael S. Tsirkin <mst@...hat.com> wrote: > > [...] >> So it seems that a sane solution would involve an extra level of >> indirection, with guest addresses being translated to host IB addresses. >> As long as you do this, maybe using an ethernet frame format makes sense. > [...] > > Yep, that's among the points we're trying to make, the way you've put > it makes it clearer. > >> - IGMP/MAC snooping in a driver is just too hairy. > > mmm, any rough idea/direction how to do that otherwise? Let me give you a non-hack recomendation. - Give up on being wire compatible with IPoIB. - Define and implement ethernet over inifiniband aka EoIB. With EoIB: - The SM would map ethernet address to inifiniband hardware addresses. - You discover which multicast addresses are of interest from the IP layer above so no snooping is necessary. - You could run queue pairs directly to hosts. Shrug. It is trivial and it will work. It will probably run into the same problems that have historically been a problem for using IPoIB (lack of stateless offloads) but shrug that is mostly a NIC firmware problem. The switches will have no trouble and interoperability will be assured. If you want to map ethernet over infiniband please map ethernet over infiniband. Don't poorly NAT ethernet into infiniband. Eric -- 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