From: tgh <wwwwww4187@sina.com.cn>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: question about io path in the front/backend
Date: Thu, 15 Nov 2007 15:04:02 +0800 [thread overview]
Message-ID: <473BEF62.2070606@sina.com.cn> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02621F51@pdsmsx411.ccr.corp.intel.com>
hi
I have read some documents and wiki about split driver in xen,and I am
confused about the I/O path ,in which a sys_read() pass through the domU
and dom0,does sys_read() in the domU pass through vfs and ,say ,ext3fs
in domU,and insert request into the requeest_queue of the
frontend-driver,is it right?
and then ,say domU sets up with a *.img file in the dom0, then what
does frontend and backend driver do?
does frontend transmit the request to the backend ,is it right?
and then what does backend driver do ? does backend transfer the
request to the phyiscal driver in the dom0 ,is it right?
or does backend transfer the request into some read()operation ,and
submit it to the vfs and ,say,ext3fs in dom0, and do another relatively
complete io path in the dom0,is it right?
or if backend transfer the request to physical driver directly, how
does the backend deal with the request's virtual address ,and how does
backend manage bio buffer ,does physical driver and backend and frontend
share the bio buffer in some way, or what does xen deal with it ?
I am confused about all that ,could someone help me
Thanks in advance
next prev parent reply other threads:[~2007-11-15 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 3:05 wbinvd optimization for pass through domain Dong, Eddie
2007-11-15 7:04 ` tgh [this message]
2007-12-04 2:58 ` question about io path in the front/backend Mark Williamson
2007-12-05 7:19 ` tgh
2007-12-07 9:25 ` tgh
2007-12-09 2:10 ` Mark Williamson
2007-12-09 5:14 ` Pradeep Singh
2007-12-09 19:47 ` Mark Williamson
2007-11-16 16:29 ` wbinvd optimization for pass through domain Keir Fraser
2007-11-19 5:08 ` Dong, Eddie
2007-11-19 11:48 ` Keir Fraser
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=473BEF62.2070606@sina.com.cn \
--to=wwwwww4187@sina.com.cn \
--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.