From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: Re: [PATCH 1/3] xen-netback: make feature-rx-notify mandatory Date: Thu, 23 Oct 2014 12:32:06 +0100 Message-ID: <20141023113206.GF9188@zion.uk.xensource.com> References: <1413983335-8307-1-git-send-email-david.vrabel@citrix.com> <1413983335-8307-2-git-send-email-david.vrabel@citrix.com> <20141023111629.GE9188@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: , , Ian Campbell , Wei Liu To: David Vrabel Return-path: Received: from smtp02.citrix.com ([66.165.176.63]:42782 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932402AbaJWLcH (ORCPT ); Thu, 23 Oct 2014 07:32:07 -0400 Content-Disposition: inline In-Reply-To: <20141023111629.GE9188@zion.uk.xensource.com> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Oct 23, 2014 at 12:16:29PM +0100, Wei Liu wrote: > On Wed, Oct 22, 2014 at 02:08:53PM +0100, David Vrabel wrote: > > Frontends that do not provide feature-rx-notify may stall because > > netback depends on the notification from frontend to wake the guest Rx > > thread (even if can_queue is false). > > > > This could be fixed but feature-rx-notify was introduced in 2006 and I > > am not aware of any frontends that do not implement this. > > > > Signed-off-by: David Vrabel > > Acked-by: Wei Liu While I can understand this patch by itself, can you elaborate a little bit on how it affects later patches? Because what I'm thinking is that this patch is not for stable while other two should go to stable. Wei.