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
| ||
|
Date: Thu, 02 Aug 2012 10:15:23 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Or Gerlitz <ogerlitz@...lanox.com> Cc: davem@...emloft.net, roland@...nel.org, netdev@...r.kernel.org, ali@...lanox.com, sean.hefty@...el.com, Erez Shitrit <erezsh@...lanox.co.il> Subject: Re: [PATCH V2 09/12] net/eipoib: Add main driver functionality Or Gerlitz <ogerlitz@...lanox.com> writes: > From: Erez Shitrit <erezsh@...lanox.co.il> > > The eipoib driver provides a standard Ethernet netdevice over > the InfiniBand IPoIB interface . > > Some services can run only on top of Ethernet L2 interfaces, and cannot be > bound to an IPoIB interface. With this new driver, these services can run > seamlessly. Do I read this code correctly that what you are doing is not tunneling ethernet over IB but instead you are removing an ethernet header and replacing it with an IB header? Do I also read this code correctly if you can't find your destination mac address in your ""neighbor table"" you do a normal IPoIB arp for the infiniband GUID? Do I read this right that if presented with a non-IPv4 or ARP packet this code will do something undefined and unpredictable? Maybe this makes some sense but just skimming it looks like you are trying to force a square peg into a round hole resulting in some weird code and some very weird maintainability issues. I am honestly surprised at this approach. I would think it would be faster and simpler to run an IB queue pair directly to the hypervisor or possibly even the guest operating system bypassing the kernel and doing all of this translation in userspace. 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