linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: sjenning@linux.vnet.ibm.com, Konrad Wilk <konrad.wilk@oracle.com>,
	minchan@kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, devel@linuxdriverproject.org,
	ngupta@vflare.org
Subject: Re: [PATCH] staging/zcache: Fix/improve zcache writeback code, tie to a config option
Date: Wed, 13 Feb 2013 09:18:17 -0800	[thread overview]
Message-ID: <20130213171817.GA14694@kroah.com> (raw)
In-Reply-To: <694a9284-7d41-48c6-a55b-634fb2912f43@default>

On Wed, Feb 13, 2013 at 08:55:29AM -0800, Dan Magenheimer wrote:
> For completeness, I thought I should add some planning items
> that ARE new functionality.  In my opinion, these can wait
> until after promotion, but mm developers may have different
> opinions:
> 
> ZCACHE FUTURE NEW FUNCTIONALITY
> 
> A. Support zsmalloc as an alternative high-density allocator
> B. Support zero-filled pages more efficiently
> C. Possibly support three zbuds per pageframe when space allows

Care to send a patch adding all of this "TODO" information to the TODO
file in the kernel so that we don't have to go through all of this again
in 3 months when I forget why I'm now rejecting your patches again?  :)

thanks,

greg k-h

  reply	other threads:[~2013-02-13 17:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 18:27 [PATCH] staging/zcache: Fix/improve zcache writeback code, tie to a config option Dan Magenheimer
2013-02-06 19:09 ` Greg KH
2013-02-06 20:51   ` Dan Magenheimer
2013-02-06 21:43     ` Greg KH
2013-02-06 22:42       ` Dan Magenheimer
2013-02-07  0:03         ` Greg KH
2013-02-11 21:43           ` Dan Magenheimer
2013-02-11 21:49             ` Greg KH
2013-02-11 22:05               ` Dan Magenheimer
2013-02-13 16:55               ` Dan Magenheimer
2013-02-13 17:18                 ` Greg KH [this message]
2013-02-12 19:40             ` Konrad Rzeszutek Wilk
2013-02-22  3:51 ` Ric Mason
2013-02-25 17:29   ` Dan Magenheimer
2013-02-26  0:12     ` Ric Mason
2013-02-26 20:17       ` Dan Magenheimer
2013-02-22  4:13 ` Ric Mason
2013-02-28 22:29   ` Dan Magenheimer
2013-03-01  0:35     ` Ric Mason
2013-02-11 22:07 Dan Magenheimer

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=20130213171817.GA14694@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=devel@linuxdriverproject.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).