[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAk-MO9fL3ir421AjtTnJHx45CP+dNpLaM=Gsbtpy_x2x4E1Ow@mail.gmail.com>
Date: Tue, 14 Mar 2017 15:25:52 +0200
From: Erez Shitrit <erezsh@....mellanox.co.il>
To: "Vishwanathapura, Niranjana" <niranjana.vishwanathapura@...el.com>
Cc: Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Erez Shitrit <erezsh@...lanox.com>,
Doug Ledford <dledford@...hat.com>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
netdev@...r.kernel.org, valex@...lanox.com,
Leon Romanovsky <leonro@...lanox.com>, saedm@...lanox.com
Subject: Re: [RFC v1 for accelerated IPoIB 04/25] IB/verb: Add ipoib_options
struct and API
On Tue, Mar 14, 2017 at 9:01 AM, Vishwanathapura, Niranjana
<niranjana.vishwanathapura@...el.com> wrote:
> On Mon, Mar 13, 2017 at 02:01:36PM -0600, Jason Gunthorpe wrote:
>>>
>>> + /* multicast */
>>> + int (*attach_mcast)(struct net_device *dev, struct ib_device
>>> *hca,
>>> + union ib_gid *gid, u16 lid, int set_qkey);
>>> + int (*detach_mcast)(struct net_device *dev, struct ib_device
>>> *hca,
>>> + union ib_gid *gid, u16 lid);
>>
>>
>> It would make more sense to store the struct ib_device pointer in the
>> struct rdma_netdev.
>>
>
> Agree that it shouldn't be a function parameters.
> For opa_vnic, I found it convenient to store ib_device pointer in client and
> device private structures as those will be available in most places anyhow.
Will add it to the rdma_netdev obj, as Jason suggested.
Thanks,
>
> Niranjana
Powered by blists - more mailing lists