From: Andi Kleen <andi@firstfloor.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>,
Johannes Stezenbach <js@sig21.net>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>,
Richard Purdie <rpurdie@openedhand.com>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Update LZO compression
Date: Thu, 16 Aug 2012 18:20:52 +0200 [thread overview]
Message-ID: <20120816162051.GK11413@one.firstfloor.org> (raw)
In-Reply-To: <502D100D.2030609@pobox.com>
> If you think a little bit, I bet you could come up with a solution that
> operates at cacheline-aligned granularity, something that would be _even
> faster_ than simply fixing the code to do aligned accesses.
Cache aligned compression is unlikely to compress anything at all.
Compression algorithms are usually by definition unaligned.
-Andi
next prev parent reply other threads:[~2012-08-16 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 23:44 [GIT PULL] Update LZO compression Markus F.X.J. Oberhumer
2012-08-14 3:15 ` Andi Kleen
2012-08-14 10:10 ` Markus F.X.J. Oberhumer
2012-08-14 12:39 ` Johannes Stezenbach
2012-08-15 12:02 ` Markus F.X.J. Oberhumer
2012-08-15 14:45 ` Johannes Stezenbach
2012-08-16 6:27 ` Markus F.X.J. Oberhumer
2012-08-16 15:06 ` Johannes Stezenbach
2012-08-16 17:25 ` Roman Mamedov
2012-08-16 17:52 ` Andi Kleen
2012-08-16 18:18 ` Geert Uytterhoeven
2012-08-16 18:57 ` james northrup
[not found] ` <CAPkEcwgv6f5B+Mrw7kzrHcZ5JZ+Yr0o=bLdoFqCB-e4CLiVx5A@mail.gmail.com>
2012-08-16 22:17 ` Andi Kleen
2012-08-17 1:23 ` Mitch Harder
2012-09-07 21:31 ` Andi Kleen
2012-08-16 15:21 ` Jeff Garzik
2012-08-16 16:20 ` Andi Kleen [this message]
2012-08-16 16:48 ` Jeff Garzik
2012-08-16 17:22 ` Johannes Stezenbach
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=20120816162051.GK11413@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=chris.mason@fusionio.com \
--cc=jgarzik@pobox.com \
--cc=js@sig21.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@oberhumer.com \
--cc=ngupta@vflare.org \
--cc=richard.weinberger@gmail.com \
--cc=rpurdie@openedhand.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).