WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] shared rings. rsp_cons, rsp_events, req_prod, req_events doc

To: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, daniel.stodden@xxxxxxxxxx, keir@xxxxxxx, JBeulich@xxxxxxxxxx
Subject: [Xen-devel] shared rings. rsp_cons, rsp_events, req_prod, req_events docs, charts, timelines?
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 16 May 2011 13:05:43 -0400
Cc:
Delivery-date: Mon, 16 May 2011 10:07:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
The current ring implementation uses these values and then macros such
as RING_HAS_UNCONSUMED_REQUESTS, FINAL_RING_CHECK, etc to determine whether
to continue or how to control the flow. Looking way back in the history
at c/s 8153 it used to have a 'server_is_sleeping' value to determine whether
to kick the back (now called 'req_event'), and the 'rsp_event' (unchanged)
to kick the frontend.

Anyhow, are there any diagrams or design docs documenting how these simple four
shared values help to control the pipeline and interrupt generation? Or how
they evolved over time to become what they are right now?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>