[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1486502926.2581.4.camel@sandisk.com>
Date: Tue, 7 Feb 2017 21:28:59 +0000
From: Bart Van Assche <Bart.VanAssche@...disk.com>
To: "dledford@...hat.com" <dledford@...hat.com>,
"niranjana.vishwanathapura@...el.com"
<niranjana.vishwanathapura@...el.com>
CC: "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, 2017-02-07 at 12:22 -0800, Vishwanathapura, Niranjana wrote:
> Intel Omni-Path Host Fabric Interface (HFI) Virtual Network Interface
> Controller (VNIC) feature supports Ethernet functionality over Omni-Path
> fabric by encapsulating the Ethernet packets between HFI nodes.
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?
Bart.
Powered by blists - more mailing lists