netdev - RE: [RFC v3 00/11] HFI Virtual Network Interface Controller (VNIC)

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1828884A29C6694DAF28B7E6B8A82373AB0E5B6C@ORSMSX109.amr.corp.intel.com>
Date:   Tue, 7 Feb 2017 21:44:26 +0000
From:   "Hefty, Sean" <sean.hefty@...el.com>
To:     Bart Van Assche <Bart.VanAssche@...disk.com>,
        "dledford@...hat.com" <dledford@...hat.com>,
        "Vishwanathapura, Niranjana" <niranjana.vishwanathapura@...el.com>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "Dalessandro, Dennis" <dennis.dalessandro@...el.com>,
        "Weiny, Ira" <ira.weiny@...el.com>
Subject: RE: [RFC v3 00/11] HFI Virtual Network Interface Controller (VNIC)

> This may have been stated before, but what is missing from this
> description
> is an explanation of why accepting an Ethernet over RDMA driver in the
> upstream kernel is considered useful. We already have an IPoIB driver,
> so
> why to add another driver to the kernel tree for communicating IP
> packets
> over an RDMA network?

This is Ethernet - not IP - encapsulation over a non-InfiniBand device/protocol.