From: Kevin Wolf <kwolf@suse.de>
To: Dutch Meyer <dmeyer@cs.ubc.ca>
Cc: Andrew Warfield <andy@cs.ubc.ca>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [4 Patches] New blktap implementation, 2nd try
Date: Fri, 31 Oct 2008 11:14:14 +0100 [thread overview]
Message-ID: <490ADA76.9010800@suse.de> (raw)
In-Reply-To: <Pine.GSO.4.60.0810310026340.13665@cascade.cs.ubc.ca>
Dutch Meyer schrieb:
> 1) deprecate-blktap. A patch to deprecate the open source blktap, by
> moving it and issuing a warning whenever it is used. No functionality
> is modified in this patch, it is just housekeeping.
Why would you want to keep the old version around if the new one is so
much better?
> 2) restore-blktap. A patch to add a new blktap implementation that is
> feature equivalent to (or better than) the current blktap. This will
> eventually replace the current blktap implementation.
Now this is a huge patch, nearly impossible to review. At a first glance
I noticed that it shares large parts with the old implementation. So
while I believe you that the first patch is only moving things around, I
really can't tell what this patch is actually doing.
It would be really useful to have the real diff, i.e. keep the old files
in patch 1 and modify them here. Best you also split this patch into a
patch for the core and one patch for the changes to each driver.
I didn't really look into the patch but merely scrolled through it and
looked at the diffstat, so maybe I'm wrong, but it seems to lack
implementations for tap:qcow2, tap:vmdk and tap:ioemu. Why that?
Kevin
next prev parent reply other threads:[~2008-10-31 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 7:44 [4 Patches] New blktap implementation, 2nd try Dutch Meyer
2008-10-31 10:14 ` Kevin Wolf [this message]
2008-10-31 17:51 ` Dutch Meyer
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=490ADA76.9010800@suse.de \
--to=kwolf@suse.de \
--cc=andy@cs.ubc.ca \
--cc=dmeyer@cs.ubc.ca \
--cc=keir.fraser@eu.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 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.