public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	dave@linux.vnet.ibm.com, cascardo@holoscopio.com,
	sjenning@linux.vnet.ibm.com
Subject: Re: [PATCH] zcache fix for 3.3-rc1.
Date: Mon, 23 Jan 2012 17:22:38 -0500	[thread overview]
Message-ID: <20120123222238.GB31852@phenom.dumpdata.com> (raw)
In-Reply-To: <20120123221155.GA10265@suse.de>

On Mon, Jan 23, 2012 at 02:11:55PM -0800, Greg KH wrote:
> On Mon, Jan 23, 2012 at 04:52:19PM -0500, Konrad Rzeszutek Wilk wrote:
> > Hey Greg,
> > 
> > I posted this patch some time ago  [https://lkml.org/lkml/2012/1/13/253]
> > but I am not seeing it in you tree.
> 
> Did you copy me on it?  I don't see it anywhere in my to-apply queues.

Ugh, I did not - I seemed to have forgotten to CC you and had assumed you
would be omnipresent and would magically pick it up. Sorry about that mishap.
> 
> > Was wondering if you could stick this patch in your tree? It fixes
> > a performance regressions which is quite noticable in small memory systems
> > where a 'swapoff' ends up taking more than it should.
> 
> So this is needed for 3.3?  How about older kernels?  3.2?  3.0?

That would be splendid if you could stick it on the stable tree :-)

> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2012-01-23 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 21:52 [PATCH] zcache fix for 3.3-rc1 Konrad Rzeszutek Wilk
2012-01-23 21:52 ` [PATCH] zcache: Set SWIZ_BITS to 8 to reduce tmem bucket lock contention Konrad Rzeszutek Wilk
2012-01-23 22:11 ` [PATCH] zcache fix for 3.3-rc1 Greg KH
2012-01-23 22:22   ` Konrad Rzeszutek Wilk [this message]
2012-01-23 22:35     ` Greg KH
2012-01-23 22:40       ` Konrad Rzeszutek Wilk

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=20120123222238.GB31852@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=cascardo@holoscopio.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.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