[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO2PR11MB008839DC3A61A4F211CC148F971E0@CO2PR11MB0088.namprd11.prod.outlook.com>
Date: Thu, 11 Aug 2016 11:46:18 +0000
From: Yuval Mintz <Yuval.Mintz@...gic.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
netdev <netdev@...r.kernel.org>
CC: "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>
Subject: RE: [PATCH net 2/4] hv_netvsc: reset vf_inject on VF removal
> +static void netvsc_inject_enable(struct net_device_context
> +*net_device_ctx) {
> + net_device_ctx->vf_inject = true;
> +}
> +
> +static void netvsc_inject_disable(struct net_device_context
> +*net_device_ctx) {
> + net_device_ctx->vf_inject = false;
> +
> + /* Wait for currently active users to drain out. */
> + while (atomic_read(&net_device_ctx->vf_use_cnt) != 0)
> + udelay(50);
> +}
That was already the behavior before, but are you certain you
want to unconditionally block without any possible timeout?
Powered by blists - more mailing lists