[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161123000643.GJ2691@lunn.ch>
Date: Wed, 23 Nov 2016 01:06:43 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Vishwanathapura, Niranjana" <niranjana.vishwanathapura@...el.com>
Cc: Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Doug Ledford <dledford@...hat.com>, linux-rdma@...r.kernel.org,
netdev@...r.kernel.org,
Dennis Dalessandro <dennis.dalessandro@...el.com>
Subject: Re: [RFC 02/10] IB/hfi-vnic: Virtual Network Interface Controller
(VNIC) Bus driver
On Tue, Nov 22, 2016 at 11:49:18AM -0800, Vishwanathapura, Niranjana wrote:
> Ok, I do understand Jason's point that we should probably not put
> this driver under drivers/infiniband/sw/.., as this driver is not a
> HCA.
> It is an ULP similar to ipoib, built on top of Omni-path
> irrespective of whether we register a hfi_vnic_bus or a direct
> custom interface with HFI1.
> This ULP will transmit and recieve Omni-path packets over the
> fabric, and is dependent on IB MAD interface and the HFI1 driver.
>
> Doug,
> Will it be acceptable if we put it under 'drivers/infiniband/ulp/hfi_vnic'?
How about turning this whole discussion around.
This is a network driver. So ask the network Maintainers where he
wants it. Send the patch to David Miller <davem@...emloft.net> and
netdev with the question, where does this code belong?
Andrew
Powered by blists - more mailing lists