From: Daniel Stodden <daniel.stodden@citrix.com>
To: Xen <xen-devel@lists.xensource.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [PATCH 0 of 7] blktap/pvops updates
Date: Thu, 03 Jun 2010 03:12:32 -0000 [thread overview]
Message-ID: <patchbomb.1275534752@agari.van.xensource.com> (raw)
Hi.
A bunch of updates to the backend/blktap2 branch.
The main difference is that all queue runs are synchronous on behalf
of tapdisk system entries now. As a consequence we can drop a couple
locks, which is good, and the .unmap vma hook, which is better.
This removes pause/unpause from the kernel interface. I don't
anticipate it's going to be missed, because that code must have been
deadlocking on sysfs node removal for quite a while. Next toolstack
update will redo pause/unpause in userspace.
On the misc side, there is some cleanup and removal of bdev
passthrough mode. The idea was nice but it never got excercised a lot.
Cheers,
Daniel
next reply other threads:[~2010-06-03 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 3:12 Daniel Stodden [this message]
2010-06-03 3:12 ` [PATCH 1 of 7] blktap: Synchronous queue dispatch Daniel Stodden
2010-06-03 3:12 ` [PATCH 2 of 7] linux: Remove unmap hook from vm_operations struct Daniel Stodden
2010-06-03 3:12 ` [PATCH 3 of 7] blktap: Remove broken sysfs pause/resume API Daniel Stodden
2010-06-03 3:12 ` [PATCH 4 of 7] blktap: Make the device destruction path synchronous Daniel Stodden
2010-06-03 3:20 ` Daniel Stodden
2010-06-03 3:12 ` [PATCH 5 of 7] blktap: Remove obsolete kernel version dependencies Daniel Stodden
2010-06-03 3:12 ` [PATCH 6 of 7] blktap: Update tap state when failing ring mmap Daniel Stodden
2010-06-03 3:12 ` [PATCH 7 of 7] blktap: Remove passthrough mode Daniel Stodden
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.1275534752@agari.van.xensource.com \
--to=daniel.stodden@citrix.com \
--cc=jeremy@goop.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 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.