From: Daniel Stodden <daniel.stodden@citrix.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0 of 4] aio event fd support to blktap2
Date: Thu, 28 Jan 2010 22:37:42 -0000 [thread overview]
Message-ID: <patchbomb.1264718262@agari.van.xensource.com> (raw)
Get blktap2 running on pvops.
This mainly adds eventfd support to the userland code. Based on some
prior cleanup to tapdisk-queue and the server object. We had most of
that in XenServer for a while, so I kept it stacked.
1. Clean up IPC and AIO init in tapdisk-server.
[I think tapdisk-ipc in blktap2 is basically obsolete.
Pending a later patch to remove it?]
2. Split tapdisk-queue into variable raw I/O backends.
This basically makes an 'ops'-struct (struct tio) out of what used
to be primarily libaio vs. an if/else hack to resort to canonical
read()/write()s where desirable.
For now, the one chosen remains as hardcoded as ever.
3. Prefer AIO eventfd support on kernels >= 2.6.22
Mainline Linux after 2.6.22 finally got I/O muxing for
AIO. Unfortunately, few systems bring the necessary libaio update
(0.3.107), xen/tools included.
Since this is just about a bunch of inline macros and an update to
reserved space in the iocb struct, let's add a compat header with
private typedefs instead.
This should obsolete tools/aio.
Misc:
- Does a runtime kernel version check. I guess this code will
need additional cpp magic on BSDs.
- Wants a PERROR macro in blktaplib.h
- Fixes a bug in tapdisk-vbd which locks up the sync io mode.
- Removed dead code in qcow2raw to make it link again.
next reply other threads:[~2010-01-28 22:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 22:37 Daniel Stodden [this message]
2010-01-28 22:37 ` [PATCH 1 of 4] blktap2: Sort out tapdisk IPC init Daniel Stodden
2010-01-28 22:37 ` [PATCH 2 of 4] blktap2: Sort out tapdisk AIO init Daniel Stodden
2010-01-28 22:37 ` [PATCH 3 of 4] blktap2: Separate tapdisk raw I/O into different backends Daniel Stodden
2010-01-28 22:37 ` [PATCH 4 of 4] blktap2: Prefer AIO eventfd support on kernels >= 2.6.22 Daniel Stodden
2010-01-29 6:55 ` [PATCH 0 of 4] aio event fd support to blktap2 Keir Fraser
2010-01-29 7:44 ` Daniel Stodden
2010-01-29 7:44 ` [PATCH 1 of 4] blktap2: Sort out tapdisk IPC init Daniel Stodden
2010-01-29 7:44 ` [PATCH 2 of 4] blktap2: Sort out tapdisk AIO init Daniel Stodden
2010-01-29 7:44 ` [PATCH 3 of 4] blktap2: Separate tapdisk raw I/O into different backends Daniel Stodden
2010-01-29 7:44 ` [PATCH 4 of 4] blktap2: Prefer AIO eventfd support on kernels >= 2.6.22 Daniel Stodden
2010-01-29 7:55 ` [PATCH 0 of 4] aio event fd support to blktap2 Daniel Stodden
2010-01-29 8:09 ` Keir Fraser
2010-01-29 8:29 ` Daniel Stodden
2010-01-29 8:45 ` Daniel Stodden
2010-01-29 8:52 ` Keir Fraser
2010-01-29 9:22 ` Daniel Stodden
2010-01-29 10:06 ` Pasi Kärkkäinen
2010-01-29 10:27 ` Daniel Stodden
2010-01-29 10:34 ` Ian Campbell
2010-01-29 10:52 ` Daniel Stodden
2010-02-02 22:53 ` David P. Quigley
2010-02-02 23:10 ` Daniel Stodden
2010-02-02 23:08 ` David P. Quigley
2010-02-02 23:23 ` David P. Quigley
2010-02-02 23:57 ` Daniel Stodden
2010-02-03 0:37 ` David P. Quigley
[not found] ` <1265219911.14885.1940.camel@agari.van.xensource.com>
[not found] ` <1265224548.19768.3.camel@moss-terrapins.epoch.ncsc.mil>
2010-02-03 19:41 ` Daniel Stodden
2010-02-03 19:47 ` Daniel Stodden
2010-02-03 19:41 ` David P. Quigley
2010-02-03 20:02 ` Daniel Stodden
2010-02-03 20:12 ` David P. Quigley
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.1264718262@agari.van.xensource.com \
--to=daniel.stodden@citrix.com \
--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).