From: Mats Petersson <mats.petersson@citrix.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xen with huffman coding
Date: Fri, 14 Dec 2012 16:34:48 +0000 [thread overview]
Message-ID: <50CB5528.2020203@citrix.com> (raw)
In-Reply-To: <CCF103FE.55C40%keir@xen.org>
On 14/12/12 16:27, Keir Fraser wrote:
> On 14/12/2012 14:49, "Mats Petersson" <mats.petersson@citrix.com> wrote:
>
>> For code and typical data, I'm not at all convinced that huffman
>> encoding (which is based on run-lengths) is the best method.
> Actually Huffman encoding is not a run-length scheme.
Ah, I'm confusing it with ccitt (or whatever it is that fax-machines
use), which uses a fixed Huffman tree to encode a set of run lengths of
black/white pixels.
Either way, looking at more than one compression mechanism may have some
value.
--
Mats
>
> -- Keir
>
>
>
>
next prev parent reply other threads:[~2012-12-14 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:32 xen with huffman coding digvijay chauhan
2012-12-14 14:49 ` Mats Petersson
2012-12-14 16:27 ` Keir Fraser
2012-12-14 16:34 ` Mats Petersson [this message]
2012-12-14 17:19 ` Keir Fraser
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=50CB5528.2020203@citrix.com \
--to=mats.petersson@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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).