From: Thanos Makatos <thanos.makatos@citrix.com>
To: xen-devel@lists.xen.org
Cc: thanos.makatos@citrix.com
Subject: [PATCH 0 of 6 RESEND v2] blktap3/sring: shared ring between tapdisk and the front-end
Date: Mon, 15 Jul 2013 12:41:23 +0100 [thread overview]
Message-ID: <patchbomb.1373888483@makatos-desktop> (raw)
This patch series introduces the shared ring used by the front-end to pass
request descriptors to tapdisk, as well as responses from tapdisk to the
front-end. Requests from this ring end up in tapdisk's standard request queue.
When the tapback daemon detects that the front-end tries to connect to the
back-end, it spawns a tapdisk and tells it to connect to the shared ring. The
shared ring is created by the tapdisk using the grant references and the event
channel port, supplied by tapback. Once the ring is created, tapdisk watches
the event channel for notifications. When a notification is received, tapdisk
extracts the request, parses it, and passes it to the standard tapdisk request
queue for processing.
Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>
next reply other threads:[~2013-07-15 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 11:41 Thanos Makatos [this message]
2013-07-15 11:41 ` [PATCH 1 of 6 RESEND v2] blktap3/sring: Headers required for compiling the shared ring Thanos Makatos
2013-07-15 11:41 ` [PATCH 2 of 6 RESEND v2] blktap3/sring: connect to/disconnect from " Thanos Makatos
2013-07-15 11:41 ` [PATCH 3 of 6 RESEND v2] blktap3/sring: extract requests from the ring, grouping of VBDs Thanos Makatos
2013-07-15 11:41 ` [PATCH 4 of 6 RESEND v2] blktap3/sring: parse ring requests and handle them over to tapdisk Thanos Makatos
2013-07-15 11:41 ` [PATCH 5 of 6 RESEND v2] blktap3/sring: stats for the shared ring between tapdisk and the front-end Thanos Makatos
2013-07-15 11:41 ` [PATCH 6 of 6 RESEND v2] blktap3/sring: Compile the shared ring into a static library Thanos Makatos
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=patchbomb.1373888483@makatos-desktop \
--to=thanos.makatos@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).