From: Dave Rodgman <dave.rodgman@arm.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
Matt Sealey <Matt.Sealey@arm.com>,
"nitingupta910@gmail.com" <nitingupta910@gmail.com>,
"markus@oberhumer.com" <markus@oberhumer.com>,
"minchan@kernel.org" <minchan@kernel.org>,
"sergey.senozhatsky.work@gmail.com"
<sergey.senozhatsky.work@gmail.com>,
"sonnyrao@google.com" <sonnyrao@google.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
nd <nd@arm.com>
Subject: [PATCH v3 0/7] lib/lzo: performance improvements
Date: Fri, 30 Nov 2018 11:47:36 +0000 [thread overview]
Message-ID: <20181130114715.27523-1-dave.rodgman@arm.com> (raw)
This patch series introduces performance improvements for lzo.
The previous version of this patchset is here:
https://lkml.org/lkml/2018/11/27/1086
On 29/11/2018 8:32 pm, Andrew Morton wrote:
> On Thu, 29 Nov 2018 10:21:53 +0000 Dave Rodgman <dave.rodgman@arm.com> wrote:
>>> OK, so it's not just "separate lzo-rle", it's also "switch zram to
>>> a new compression algorithm by default". I'd say that usually I'd
>>> expect this to be separate patches.
>>
>> Yes, fair point. akpm has picked this up now though, so probably a bit
>> late to break it out into a separate patch?
>
> That's fine. akpm is flexible ;) Whatever produces the best overall
> result in the permanent record, please.
Thanks - I've separated this as suggested. I've also fixed up the commit
message for patch 1 (tidy-up ifdefs) which looks like it was accidentally
changed (please ignore if the change was intentional).
Dave
next reply other threads:[~2018-11-30 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 11:47 Dave Rodgman [this message]
2018-11-30 11:47 ` [PATCH 1/8] lib/lzo: tidy-up ifdefs Dave Rodgman
2018-11-30 11:47 ` [PATCH 2/8] lib/lzo: clean-up by introducing COPY16 Dave Rodgman
2018-11-30 12:27 ` David Laight
2018-11-30 11:47 ` [PATCH 3/8] lib/lzo: enable 64-bit CTZ on Arm Dave Rodgman
2018-11-30 11:47 ` [PATCH 4/8] lib/lzo: 64-bit CTZ on arm64 Dave Rodgman
2018-11-30 11:47 ` [PATCH 5/8] lib/lzo: fast 8-byte copy " Dave Rodgman
2018-11-30 11:47 ` [PATCH 6/8] lib/lzo: implement run-length encoding Dave Rodgman
2018-11-30 11:47 ` [PATCH 7/8] lib/lzo: separate lzo-rle from lzo Dave Rodgman
2018-11-30 11:47 ` [PATCH 8/8] zram: default to lzo-rle instead of lzo Dave Rodgman
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=20181130114715.27523-1-dave.rodgman@arm.com \
--to=dave.rodgman@arm.com \
--cc=Matt.Sealey@arm.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@oberhumer.com \
--cc=minchan@kernel.org \
--cc=nd@arm.com \
--cc=nitingupta910@gmail.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sonnyrao@google.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
all inboxes | Powered by JetHome®