From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: RING_HAS_UNCONSUMED_REQUESTS oddness
Date: Thu, 13 Mar 2014 10:02:58 +0000
Message-ID: <1394704978.25873.9.camel@kazak.uk.xensource.com>
References: <5318987C.3030303@citrix.com>
	<1394552666.30915.64.camel@kazak.uk.xensource.com>
	<531F9B17.5060107@citrix.com>
	<1394620083.21145.21.camel@kazak.uk.xensource.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD0282CBF@AMSPEX01CL01.citrite.net>
	<53207226.7090002@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02833BD@AMSPEX01CL01.citrite.net>
	<20140312154249.GP19620@zion.uk.xensource.com>
	<532087BB.6000100@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD0283744@AMSPEX01CL01.citrite.net>
	<5320B029.8040604@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD028577E@AMSPEX01CL01.citrite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1WO2U3-0005P5-La
	for xen-devel@lists.xenproject.org; Thu, 13 Mar 2014 10:03:27 +0000
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD028577E@AMSPEX01CL01.citrite.net>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>, Wei Liu <wei.liu2@citrix.com>, Zoltan Kiss <zoltan.kiss@citrix.com>, "Tim
	(Xen.org)" <tim@xen.org>
List-Id: xen-devel@lists.xenproject.org

On Thu, 2014-03-13 at 09:26 +0000, Paul Durrant wrote:
> guarantee that netback will always respond in order on the rx ring.

I don't believe this is guaranteed byt the protocol, even if it happens
to work out that way for the Linux netback implementation.

Ian.