From: Kaushik Bhandankar <kaushikb@cc.gatech.edu>
To: Xen-devel <xen-devel@lists.xensource.com>
Subject: doubt: Block IO multiple ring protocol
Date: Thu, 15 Nov 2007 02:54:11 -0500 [thread overview]
Message-ID: <473BFB23.9050001@cc.gatech.edu> (raw)
Hello,
Looking at linux-2.6-xen-sparse/drivers/xen/blkback/blkback.c, I had
following doubts (also looked at the following changeset which
introduces multiple ring protocols:
http://lists.xensource.com/archives/html/xen-changelog/2007-01/msg00413.html)
1) When a block IO request is made by guest, do_block_io_op() obtains
the 'req' from appropriate ring based on blk_protocol (and invokes
dispatch_rw_block_io()) but the "req_cons" is incremented for the
"common" ring.. Where is the "req_cons" being incremented for the
corresponding ring (native, x86_32 or x86_64) ?
2) For sending back the response, make_response() copies the "resp" on
the appropriate ring based on blk_protocol but increments the
"rsp_prod_pvt" for the "common" ring. Where is the "rsp_prod_pvt" being
incremented for the corresponding ring (native, x86_32 or x86_64) ?
Looking at xen/include/public/io/ring.h, I couldnt really figure things
out looking at the macros? Am not really sure how the counters get
incremented/decremented for each protocol ring during block
request/response phase ...Any hint is appreciated....
--Kaushik
reply other threads:[~2007-11-15 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=473BFB23.9050001@cc.gatech.edu \
--to=kaushikb@cc.gatech.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.