[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM5PR03MB2538CF7A32AD65F437634039CA1E0@DM5PR03MB2538.namprd03.prod.outlook.com>
Date: Thu, 11 Aug 2016 15:38:05 +0000
From: Haiyang Zhang <haiyangz@...rosoft.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
KY Srinivasan <kys@...rosoft.com>
Subject: RE: [PATCH net 1/4] hv_netvsc: don't lose VF information
> -----Original Message-----
> From: Vitaly Kuznetsov [mailto:vkuznets@...hat.com]
> Sent: Thursday, August 11, 2016 6:59 AM
> To: netdev@...r.kernel.org
> Cc: devel@...uxdriverproject.org; linux-kernel@...r.kernel.org; Haiyang
> Zhang <haiyangz@...rosoft.com>; KY Srinivasan <kys@...rosoft.com>
> Subject: [PATCH net 1/4] hv_netvsc: don't lose VF information
>
> struct netvsc_device is not suitable for storing VF information as this
> structure is being destroyed on MTU change / set channel operation (see
> rndis_filter_device_remove()). Move all VF related stuff to struct
> net_device_context which is persistent.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
Acked-by: Haiyang Zhang <haiyangz@...rosoft.com>
Powered by blists - more mailing lists