From: Luis Henriques <luis.henriques@canonical.com>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jon Medhurst <tixy@linaro.org>,
Alexandre Courbot <acourbot@nvidia.com>,
stable@vger.kernel.org, linaro-kernel@lists.linaro.org,
linux-kernel@vger.kernel.org
Subject: Re: Possible stable fix for decompressor speed
Date: Mon, 3 Feb 2014 13:59:12 +0000 [thread overview]
Message-ID: <20140203135912.GC5258@hercules> (raw)
In-Reply-To: <20140128161428.GO11841@sirena.org.uk>
On Tue, Jan 28, 2014 at 04:14:28PM +0000, Mark Brown wrote:
> The changes in patch 1431574a1c4c (lib/decompressors: fix "no limit"
> output buffer length) avoid doing decompression a byte at a time when
> decompressing into high physical addresses using a small, well isolated
> change. The patch can give a very noticable improvement in kernel boot
> times on affected systems, for example with one ARM system this reduces
> the total time to boot the kernel by more than a third.
>
> Would you consider this patch for stable? It doesn't quite fit within
> the criteria but you've indicated in the past that such isolated and
> well supported changs can be acceptable anyway. If it's not OK for
> stable it seems like it should be a good candidate for LTSI.
Thanks Mark, I'm queuing this for the 3.5 and the 3.11 kernels as well.
Cheers,
--
Luis
prev parent reply other threads:[~2014-02-03 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 16:14 Possible stable fix for decompressor speed Mark Brown
2014-01-28 16:28 ` Greg Kroah-Hartman
2014-02-03 13:59 ` Luis Henriques [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=20140203135912.GC5258@hercules \
--to=luis.henriques@canonical.com \
--cc=acourbot@nvidia.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tixy@linaro.org \
/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).