From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 compression
Date: Wed, 20 Oct 2004 16:06:23 +0400 [thread overview]
Message-ID: <417654BF.4010703@yandex.ru> (raw)
In-Reply-To: <417651AD.50001@inf.u-szeged.hu>
> If the "one step" means that you would like to use only one
> jffs2_decompress/... call than the answer is no.
Ok, thanks for answer, I suspected so. But I was confused by the
interface function jffs2_free_comprbuf, and slender hope have appeared. :-)
>
> But I can imagine a solution, where you can call jffs2_compress
> separatedly for the small buffers, and you can uncompress it using a loop.
>
> The compression buffer can be something like the following:
> - original_size_of_small_buffer1
> - compressed_size_of_small_buffer1
> - comprtype (return value of jffs2_compress)
> - compressed data1
> - original_size_of_small_buffer2
> - compressed_size_of_small_buffer2
> - comprtype (return value of jffs2_compress)
> - compressed data2
> ...
>
> I don't know it is OK for you or not.
It would be OK, if I don't have to store the sizes of original buffers
(original_size_of_small_buffer1, etc) in the node... This is because the
number of input small buffers isn't fixed...
Thank you.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2004-10-20 12:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 17:14 JFFS2 bugfix Artem B. Bityuckiy
2004-10-18 11:57 ` Ferenc Havasi
2004-10-18 12:16 ` Artem B. Bityuckiy
2004-10-19 7:57 ` Ferenc Havasi
2004-10-19 8:06 ` Artem B. Bityuckiy
2004-10-19 9:16 ` David Woodhouse
[not found] ` <4174D508.8050508@yandex.ru>
2004-10-19 10:09 ` JFFS2 compression Ferenc Havasi
2004-10-19 10:14 ` David Woodhouse
2004-10-20 9:16 ` Ferenc Havasi
2004-10-20 9:16 ` David Woodhouse
2004-10-20 11:13 ` Artem B. Bityuckiy
2004-10-20 11:53 ` Ferenc Havasi
2004-10-20 12:06 ` Artem B. Bityuckiy [this message]
2004-10-19 10:48 ` Artem B. Bityuckiy
2004-10-19 12:06 ` Ferenc Havasi
2004-10-19 12:19 ` Artem B. Bityuckiy
2004-10-19 13:43 ` David Woodhouse
2004-10-19 14:07 ` Ferenc Havasi
2004-10-19 14:08 ` David Woodhouse
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=417654BF.4010703@yandex.ru \
--to=abityuckiy@yandex.ru \
--cc=havasi@inf.u-szeged.hu \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.