From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: jaredeh@gmail.com, 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 04/10] AXFS: axfs_inode.c
Date: Fri, 22 Aug 2008 03:22:45 +0100 [thread overview]
Message-ID: <48AE22F5.3000309@lougher.demon.co.uk> (raw)
In-Reply-To: <200808211417.14425.arnd@arndb.de>
Arnd Bergmann wrote:
> On Thursday 21 August 2008, Jared Hulbert wrote:
>> + array_index = AXFS_GET_INODE_ARRAY_INDEX(sbi, ino_number);
>> + array_index += page->index;
>> +
>> + node_index = AXFS_GET_NODE_INDEX(sbi, array_index);
>> + node_type = AXFS_GET_NODE_TYPE(sbi, array_index);
>> +
>> + if (node_type == Compressed) {
>> + /* node is in compessed region */
>> + cnode_offset = AXFS_GET_CNODE_OFFSET(sbi, node_index);
>> + cnode_index = AXFS_GET_CNODE_INDEX(sbi, node_index);
>> + down_write(&sbi->lock);
>> + if (cnode_index != sbi->current_cnode_index) {
>> + /* uncompress only necessary if different cblock */
>> + ofs = AXFS_GET_CBLOCK_OFFSET(sbi, cnode_index);
>> + len = AXFS_GET_CBLOCK_OFFSET(sbi, cnode_index + 1);
>> + len -= ofs;
>> + axfs_copy_data(sb, cblk1, &(sbi->compressed), ofs, len);
>> + axfs_uncompress_block(cblk0, cblk_size, cblk1, len);
>> + sbi->current_cnode_index = cnode_index;
>> + }
>> + downgrade_write(&sbi->lock);
>> + max_len = cblk_size - cnode_offset;
>> + len = max_len > PAGE_CACHE_SIZE ? PAGE_CACHE_SIZE : max_len;
>> + src = (void *)((unsigned long)cblk0 + cnode_offset);
>> + memcpy(pgdata, src, len);
>> + up_read(&sbi->lock);
>
> This looks very nice, but could use some comments about how the data is
> actually stored on disk. It took me some time to figure out that it actually
> allows to do tail merging into compressed blocks, which I was about to suggest
> you implement ;-). Cramfs doesn't have them, and I found that they are the
> main reason why squashfs compresses better than cramfs, besides the default
> block size, which you can change on either one.
Squashfs has much larger block sizes than cramfs (last time I looked it
was limited to 4K blocks), and it compresses the metadata which helps to
get better compression. But tail merging (fragments in Squashfs
terminology) is obviously a major reason why Squashfs gets good compression.
The AXFS code is rather obscure but it doesn't look to me that it does
tail merging. The following code wouldn't work if the block in question
was a tail contained in a larger block. It assumes the block extends to
the end of the compressed block (cblk_size - cnode_offset).
>> + max_len = cblk_size - cnode_offset;
>> + len = max_len > PAGE_CACHE_SIZE ? PAGE_CACHE_SIZE :
max_len;
>> + src = (void *)((unsigned long)cblk0 + cnode_offset);
>> + memcpy(pgdata, src, len);
Perhaps the AXFS authors could clarify this?
Phillip
next prev parent reply other threads:[~2008-08-22 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 5:45 [PATCH 04/10] AXFS: axfs_inode.c Jared Hulbert
2008-08-21 8:35 ` Carsten Otte
2008-08-21 11:35 ` Arnd Bergmann
2008-08-21 12:17 ` Arnd Bergmann
2008-08-21 15:06 ` Jared Hulbert
2008-08-21 15:12 ` Arnd Bergmann
2008-08-22 2:22 ` Phillip Lougher [this message]
2008-08-22 3:23 ` Jared Hulbert
2008-08-22 3:29 ` Phillip Lougher
2008-08-22 10:00 ` Arnd Bergmann
2008-08-22 17:08 ` Phillip Lougher
2008-08-22 17:19 ` Jörn Engel
2008-08-22 18:04 ` Jared Hulbert
2008-08-22 0:21 ` Phillip Lougher
2008-08-22 3:27 ` Jared Hulbert
2008-08-22 3:46 ` Phillip Lougher
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=48AE22F5.3000309@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=Linux-kernel@vger.kernel.org \
--cc=arnd@arndb.de \
--cc=cotte@de.ibm.com \
--cc=jaredeh@gmail.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).