From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: devel@linuxdriverproject.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ngupta@vflare.org,
Konrad Wilk <konrad.wilk@oracle.com>,
minchan@kernel.org
Subject: RE: [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge
Date: Sat, 18 Aug 2012 12:10:08 -0700 (PDT) [thread overview]
Message-ID: <875d22f4-47f4-4dc0-81b7-0a9da59b202d@default> (raw)
In-Reply-To: <502EC67F.4070603@linux.vnet.ibm.com>
[Seth re new redesigned codebase]
> From: Seth Jennings [mailto:sjenning@linux.vnet.ibm.com]
> Sent: Friday, August 17, 2012 4:33 PM
>
> So I can't support this patchset, citing the performance
> degradation and the fact that this submission is
> unreviewable due to it being one huge monolithic patchset on
> top of an existing codebase.
[Dan re old demo codebase]
> From: Dan Magenheimer
> Sent: Wednesday, August 08, 2012 11:48 AM
> Subject: RE: [PATCH 0/4] promote zcache from staging
>
> Sorry, but FWIW my vote is still a NACK. IMHO zcache needs major
> work before it should be promoted, and I think we should be spending
> the time fixing the known flaws rather than arguing about promoting
> "demo" code.
:-#
"Well, pahdner," drawls the Colorado cowboy (Dan) to the Texas
cowboy (Seth), "I reckon we gots us a good old fashioned standoff."
"What say we settle this like men, say six-shooters at
twenty paces?"
:-)
Seriously, maybe we should consider a fork? Zcache and zcache2?
(I am REALLY away from email for a few days starting NOW.)
Dan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-08-18 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 22:31 [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge Dan Magenheimer
2012-08-16 22:31 ` [PATCH 1/3] Remove old zcache and ramster staging drivers to prep for new code base Dan Magenheimer
2012-08-16 22:31 ` [PATCH 2/3] Move to new zcache codebase Dan Magenheimer
2012-08-16 22:31 ` [PATCH 3/3] Move to new codebase for ramster, re-merged with " Dan Magenheimer
2012-08-16 22:48 ` [PATCH 0/3] staging: zcache+ramster: move to new code base and re-merge Greg KH
2012-08-16 22:53 ` Dan Magenheimer
2012-08-16 23:08 ` Greg KH
2012-08-17 0:19 ` Dan Magenheimer
2012-08-17 22:32 ` Seth Jennings
2012-08-18 19:10 ` Dan Magenheimer [this message]
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=875d22f4-47f4-4dc0-81b7-0a9da59b202d@default \
--to=dan.magenheimer@oracle.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.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).