From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com,
Ian Campbell <Ian.Campbell@eu.citrix.com>,
daniel.stodden@citrix.com, keir@xen.org, JBeulich@novell.com
Subject: shared rings. rsp_cons, rsp_events, req_prod, req_events docs, charts, timelines?
Date: Mon, 16 May 2011 13:05:43 -0400 [thread overview]
Message-ID: <20110516170543.GA28949@dumpdata.com> (raw)
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?
next reply other threads:[~2011-05-16 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 17:05 Konrad Rzeszutek Wilk [this message]
2011-05-16 20:03 ` shared rings. rsp_cons, rsp_events, req_prod, req_events docs, charts, timelines? Daniel Stodden
2011-05-16 21:16 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110516170543.GA28949@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=daniel.stodden@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).