linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jared Hulbert" <jaredeh@gmail.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
	Linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org,
	linux-mtd <linux-mtd@lists.infradead.org>,
	"Jörn Engel" <joern@logfs.org>,
	tim.bird@am.sony.com, cotte@de.ibm.com, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 03/10] AXFS: axfs.h
Date: Fri, 22 Aug 2008 11:12:32 -0700	[thread overview]
Message-ID: <6934efce0808221112p64fe1346kc5530ca71dbb108b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808221402170.17105@vixen.sonytel.be>

>> So do I understand right that 3 bytes is your minimum size, and going
>> smaller than that would not be helpful? Otherwise I would assume that
>> storing a '5' should only take one byte instead of three.

Right.  But you need 3 bytes to store the maximum value 0x0a0000

If we had:
0x0000000000000003
0x00000000000000FF
0x000000000000000A

You would only need a 1 byte depth.

> From the paper, the minimum size (called `depth') is 1.

Correct the depth can be from 1 to 8 bytes.  The depth is determined
by the maximum value in the array.

>> I don't unsterstand yet why you store the length of each word separate
>> from the word. Most variable-length codes store that implicitly in
>> the data itself, e.g. in the upper three bits, so that for storing
>> 0x5, 0x1001, 0xa0000, this could e.g. end up as 0x054010014a0000,
>> which is shorter than what you have, but not harder to decode.
>
> AFAIU, the length (`depth') of each word is not stored separate, as the
> depth is the same for all values in the same table.

That is correct.  Each table has a single depth stored in the region descriptor.

  reply	other threads:[~2008-08-22 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21  5:45 [PATCH 03/10] AXFS: axfs.h Jared Hulbert
2008-08-21  7:51 ` Carsten Otte
2008-08-21 11:31 ` Arnd Bergmann
2008-08-21 20:05   ` Jared Hulbert
2008-08-21 12:24 ` Arnd Bergmann
2008-08-21 22:40   ` Jared Hulbert
2008-08-22 11:27     ` Arnd Bergmann
2008-08-22 12:04       ` Geert Uytterhoeven
2008-08-22 18:12         ` Jared Hulbert [this message]
2008-08-21 13:10 ` Daniel Walker
2008-08-21 20:07   ` Jared Hulbert

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=6934efce0808221112p64fe1346kc5530ca71dbb108b@mail.gmail.com \
    --to=jaredeh@gmail.com \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=arnd@arndb.de \
    --cc=cotte@de.ibm.com \
    --cc=joern@logfs.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=tim.bird@am.sony.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).