From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: linux-kernel@vger.kernel.org, Nitin Gupta <ngupta@vflare.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Jerome Marchand <jmarchan@redhat.com>
Subject: Re: [PATCH v2 0/4]zram: locking redesign
Date: Tue, 14 Jan 2014 17:34:19 -0800 [thread overview]
Message-ID: <20140114173419.3122b69f2bbb1a311bfa65a2@linux-foundation.org> (raw)
In-Reply-To: <20140115012948.GE1992@bbox>
On Wed, 15 Jan 2014 10:29:48 +0900 Minchan Kim <minchan@kernel.org> wrote:
> Oops, I missed Tested-by from Sergey. Really, sorry.
> If I have a chance to resend from any review, I will add. Otherwise,
> Andrew, Could you add his tested-by?
Sure.
I normally wouldn't consider such a patchset this late in the kernel
cycle. But these patches speeds up some writes by 10x and zram is
officially still in staging/. So I guess we could squeak these into
3.14.
Prompt review and testing by others would be appreciated, please.
next prev parent reply other threads:[~2014-01-15 1:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 1:11 Minchan Kim
2014-01-15 1:11 ` [PATCH v2 1/4] zram: use atomic operation for stat Minchan Kim
2014-01-15 1:11 ` [PATCH v2 2/4] zram: introduce zram->tb_lock Minchan Kim
2014-01-15 1:11 ` [PATCH v2 3/4] zram: remove workqueue for freeing removed pending slot Minchan Kim
2014-01-15 1:11 ` [PATCH v2 4/4] zram: Remove zram->lock in read path and change it with mutex Minchan Kim
2014-01-15 1:29 ` [PATCH v2 0/4]zram: locking redesign Minchan Kim
2014-01-15 1:34 ` Andrew Morton [this message]
2014-01-15 9:21 ` Jerome Marchand
2014-01-15 9:25 ` Sergey Senozhatsky
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=20140114173419.3122b69f2bbb1a311bfa65a2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky@gmail.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
Powered by JetHome