All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: linux-kernel@vger.kernel.org,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [Announce] Squashfs 2.1 released (compressed filesystem)
Date: Sun, 12 Dec 2004 12:01:12 +0100	[thread overview]
Message-ID: <20041212110112.GE17946@alpha.home.local> (raw)
In-Reply-To: <41BA0245.4050502@lougher.demon.co.uk>

Hi Phillip,

> Many smaller improvements have also been made in this release, and there 
> are, for the first time, the results of some tests of Squashfs lookup 
> and I/O performance against Zisofs, Cloop, and CRAMFS.

I've checked you tests, numbers are appealing :-)

BTW, you need to apply the following patch to build mksquashfs with gcc < 3.

Thanks for still improving this great FS !
Willy

--- squashfs2.1/squashfs-tools/mksquashfs.c.orig	Sun Dec 12 12:10:35 2004
+++ squashfs2.1/squashfs-tools/mksquashfs.c	Sun Dec 12 12:14:55 2004
@@ -526,11 +526,10 @@
 	else if(type == SQUASHFS_LDIR_TYPE) {
 		int i;
 		unsigned char *p;
+		squashfs_ldir_inode_header *dir = &inode_header.ldir, *inodep;
 
 		if(byte_size >= 1 << 27)
 			BAD_ERROR("directory greater than 2^27-1 bytes!\n");
-
-		squashfs_ldir_inode_header *dir = &inode_header.ldir, *inodep;
 
 		inode = get_inode(sizeof(*dir) + i_size);
 		inodep = (squashfs_ldir_inode_header *) inode;



  parent reply	other threads:[~2004-12-12 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10 20:08 [Announce] Squashfs 2.1 released (compressed filesystem) Phillip Lougher
2004-12-11  1:33 ` Greg KH
2004-12-11  5:15   ` Phillip Lougher
2004-12-11 15:39     ` Greg KH
2004-12-11 15:55       ` nat/masquerade with 2.6.x Antonio Pérez
2004-12-13  1:28         ` proc/sys/net/ipv4/tcp_bic Antonio Pérez
2004-12-12 11:01 ` Willy Tarreau [this message]
2004-12-14  4:30   ` [Announce] Squashfs 2.1 released (compressed filesystem) 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=20041212110112.GE17946@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    /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.