mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nitin Gupta" <nitingupta910@gmail.com>
To: "Bret Towe" <magnade@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	"Richard Purdie" <richard@openedhand.com>,
	linux-mm-cc@laptop.org, "Satyam Sharma" <satyam.sharma@gmail.com>
Subject: Re: [RFC] LZO de/compression support - take 3
Date: Fri, 25 May 2007 10:40:41 +0530	[thread overview]
Message-ID: <4cefeab80705242210k1169d85k97ce803de02dbc2a@mail.gmail.com> (raw)
In-Reply-To: <dda83e780705241938h2dadeeb9p61c9294ddfd96990@mail.gmail.com>

On 5/25/07, Bret Towe <magnade@gmail.com> wrote:
> On 5/24/07, Nitin Gupta <nitingupta910@gmail.com> wrote:
> > On 5/23/07, Bret Towe <magnade@gmail.com> wrote:
> > > On 5/23/07, Nitin Gupta <nitingupta910@gmail.com> wrote:
> >
> > > > For now, tested on x86 only.
> > >
> > > If you have a program to test this I can run it on an amd64 and a g4 ppc
> > >
> >
> > Attached is the kernel module (compress-test) to test this LZO code.
> > Just compile this module against 2.6.22-rc2 with this LZO patch. Then
> > testing can be done as:
> > 1- Mount DebugFS somewhere e.g:
> > mkdir /debug; mount -t debugfs debugfs /debug
> > 2- Load the module and do:
> > cat /path/to/some_file > /debug/compress_test/compress
> > (/var/log/messages should show that compression was successful)
> > 3- Then decompress this file as:
> > cat /debug/compress_test/decompress > /tmp/t
> > (/var/log/messages should show that decompression was successful)
> > 4- For extra verification do:
> > diff /tmp/t /path/to/some_file   -- O/P must be empty
> >
> >
>
> the test worked fine on amd64
> from dmesg:
> LZO compress successful: orig_size=17448, comp_size=8183
> LZO decompress successful: decomp_size=17448
>
> and input and output files I gave it:
> sha1sum test-input output
> 2221c586e3eb869af7f4333d4f56b441b9aa8414  test-input
> 2221c586e3eb869af7f4333d4f56b441b9aa8414  output
>

Good to know it worked correctly on 64-bit system too. I will also
add exporting benchmarking figures soon.

> (will be giving the ppc box the same file to test btw when I get to it)
>
> and I don't know if it matters much but I tried feeding it a 260k file
> and it didn't like it
>
> cat /usr/bin/yelp > /debug/compress_test/compress
> cat: write error: No space left on device
>

Ah! I forgot to mention that max file size to feed is 256K (this was
just for simplicity of compress-test module implementation).

Thanks for your testing.

- Nitin

  reply	other threads:[~2007-05-25  5:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  8:27 Nitin Gupta
2007-05-23 10:53 ` Michael-Luke Jones
2007-05-23 11:39   ` Nitin Gupta
2007-05-23 13:57     ` Michael-Luke Jones
2007-05-23 14:03       ` Nitin Gupta
2007-05-23 14:10         ` Michael-Luke Jones
2007-05-23 14:21           ` Nitin Gupta
2007-05-23 14:33             ` Michael-Luke Jones
2007-05-24 22:41               ` Richard Purdie
2007-05-24 22:54                 ` Andrew Morton
2007-05-24 23:00                   ` Richard Purdie
2007-05-23 16:16             ` Andrew Morton
2007-05-23 16:49               ` Richard Purdie
2007-05-24  4:04                 ` Nitin Gupta
2007-05-25 10:42                   ` Pavel Machek
2007-05-26 10:23                     ` Michael-Luke Jones
2007-05-26 11:17                     ` Nitin Gupta
2007-05-23 14:50 ` Bret Towe
2007-05-24 13:48   ` Nitin Gupta
2007-05-25  2:38     ` Bret Towe
2007-05-25  5:10       ` Nitin Gupta [this message]
2007-05-25 17:02         ` Bret Towe
2007-05-25 17:33           ` Nitin Gupta
2007-05-26 11:30           ` Nitin Gupta
2007-05-27  3:39             ` Bret Towe
2007-05-23 19:34 ` Satyam Sharma
2007-05-24  4:37   ` Nitin Gupta
2007-05-24 10:49     ` Satyam Sharma
2007-05-24  8:25   ` Richard Purdie
2007-05-24 11:07     ` Satyam Sharma
2007-05-24 14:29       ` Nitin Gupta
2007-05-24 19:12         ` Satyam Sharma
2007-05-24 14:20     ` Nitin Gupta
2007-05-24 20:09       ` Satyam Sharma

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=4cefeab80705242210k1169d85k97ce803de02dbc2a@mail.gmail.com \
    --to=nitingupta910@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm-cc@laptop.org \
    --cc=magnade@gmail.com \
    --cc=richard@openedhand.com \
    --cc=satyam.sharma@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

all inboxes | Powered by JetHome®