From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [RFC][PATCH] dm-cache (block level disk cache target): UPDATE
Date: Wed, 19 Oct 2011 10:34:26 +0200 [thread overview]
Message-ID: <4E9E8B92.5050204@suse.de> (raw)
In-Reply-To: <CAGWyFtpLuciqc7Q=2GfnkBrQCRoq91qh2RwWby7UhEAEcZkCbQ@mail.gmail.com>
On 10/18/2011 10:48 PM, Stephen Bromfield wrote:
> A new patch for the 2.6.39 kernel.
>
> Signed-off-by: Ming Zhao<dm-cache@googlegroups.com>
>
Hmm? This is implementation #1 out of three.
And, incidentally, the least maintained; 2.3.39 isn't exactly the
most recent kernel.
(Otherwise one does wonder why Ming Zhao hasn't posted it himself).
(Incidentally, can we have a rule that the person sending a patch
_has_ to be listed as 'Signed-off-by', ie has to be the one actually
working on it?)
flashcache and that one from Tao Ma & Coly Li are the other two
versions of the same beast, all sharing the same codebase.
Not to mention my (slightly different) implementation which I'll be
presenting at LinuxCon Europe next week.
So maybe, just maybe, we should get out heads together and discuss
the merits and shortcomings of the various implementations.
And decide on a single implementation, not 4. Or a framework
allowing for all these variances.
But so it's hard to see why this implementation should go upstream
and none of the others.
And I somehow doubt Alasdair would agree on having several
implementations on the same topic.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2011-10-19 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 20:46 [RFC][PATCH] dm-cache (block level disk cache target): UPDATE Stephen Bromfield
2011-10-18 20:48 ` Stephen Bromfield
2011-10-19 8:34 ` Hannes Reinecke [this message]
2011-10-18 22:19 ` Andi Kleen
2011-10-19 16:17 ` Stephen Bromfield
2011-10-19 16:25 ` Andi Kleen
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=4E9E8B92.5050204@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.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.