lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 7 Feb 2017 16:54:16 -0800
From:   "Vishwanathapura, Niranjana" <niranjana.vishwanathapura@...el.com>
To:     Bart Van Assche <Bart.VanAssche@...disk.com>
Cc:     "dledford@...hat.com" <dledford@...hat.com>,
        "sean.hefty@...el.com" <sean.hefty@...el.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "dennis.dalessandro@...el.com" <dennis.dalessandro@...el.com>,
        "ira.weiny@...el.com" <ira.weiny@...el.com>
Subject: Re: [RFC v3 00/11] HFI Virtual Network Interface Controller (VNIC)

On Tue, Feb 07, 2017 at 09:58:50PM +0000, Bart Van Assche wrote:
>On Tue, 2017-02-07 at 21:44 +0000, Hefty, Sean wrote:
>> This is Ethernet - not IP - encapsulation over a non-InfiniBand device/protocol.
>
>That's more than clear from the cover letter. In my opinion the cover letter
>should explain why it is considered useful to have such a driver upstream
>and what the use cases are of encapsulating Ethernet frames inside RDMA
>packets.
>

We believe on our HW, HFI VNIC design gives better hardware resource usage 
which is also scalable and hence room for better performance.
Also as evident in the cover letter, it gives us better manageability by 
defining virtual Ethernet switches overlaid on the fabric and
use standard Ethernet support provided by Linux.

Niranjana
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ