Currently, squashfs fragments' cache size is only determined by
config option CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE. Users have
no way to change the value when they get the binary kernel.
Now make it be configured during booting or inserting module.
Signed-off-by: Qixuan Wu
Signed-off-by: Chen Jie
Add support for reading file systems compressed with the
LZ4 compression algorithm.
This patch adds the LZ4 decompressor wrapper code.
Signed-off-by: Phillip Lougher
---
fs/squashfs/lz4_wrapper.c | 142 +
fs/squashfs/squashfs_fs.h |1 +
2 files c
On Mon, 2013-07-22 at 03:21 +0100, Phillip Lougher wrote:
> Add support for reading file systems compressed with the
> LZ4 compression algorithm.
Some whitespace trivia and a naming comment.
> diff --git a/fs/squashfs/lz4_wrapper.c b/fs/squashfs/lz4_wrapper.c
[]
> +static void *lz4_init(struct sq
Add support for reading file systems compressed with the
LZ4 compression algorithm.
This patch adds the LZ4 decompressor wrapper code.
Signed-off-by: Phillip Lougher
---
fs/squashfs/lz4_wrapper.c | 163 +
fs/squashfs/squashfs_fs.h |1 +
2 files c
Phillip Lougher <[EMAIL PROTECTED]> wrote:
>
> Andrew Morton wrote:
> > Phillip Lougher <[EMAIL PROTECTED]> wrote:
> >>
> >>+static struct inode *squashfs_iget(struct super_block *s, squashfs_inode
> >>inode)
> >>+{
> >>+ struct inode *i;
> >>+ squashfs_sb_info *msBlk = (squashfs_sb_info *)s->
Andrew Morton wrote:
Phillip Lougher <[EMAIL PROTECTED]> wrote:
+static struct inode *squashfs_iget(struct super_block *s, squashfs_inode
inode)
+{
+ struct inode *i;
+ squashfs_sb_info *msBlk = (squashfs_sb_info *)s->s_fs_info;
+ squashfs_super_block *sBlk = &msBlk->sBlk;
+
On Tue, 15 Mar 2005 17:50:02 -0800, Junio C Hamano <[EMAIL PROTECTED]> wrote:
> > "PJ" == Paul Jackson <[EMAIL PROTECTED]> writes:
>
> PJ> There is not a concensus (nor a King Penguin dictate) between the
> PJ> "while(1)" and "for(;;)" style to document.
>
> FWIW, linux-0.01 has four uses of
> the King Penguin used these two constructs with consistency:
Nice distinction - thanks.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373,
1.925.600.0401
-
To unsubscribe
> "PJ" == Paul Jackson <[EMAIL PROTECTED]> writes:
PJ> There is not a concensus (nor a King Penguin dictate) between the
PJ> "while(1)" and "for(;;)" style to document.
FWIW, linux-0.01 has four uses of "while (1)" and two uses of
"for (;;)" ;-).
./fs/inode.c: while (1) {
./fs/namei.c: w
> >>Shouldn't issues like this be in the coding style document?
There is not a concensus (nor a King Penguin dictate) between the
"while(1)" and "for(;;)" style to document. If this were a
frequently asked question, I suppose someone would eventually
note in a coding style doc that either style i
Matt Mackall wrote:
On Tue, Mar 15, 2005 at 03:50:26PM +, Phillip Lougher wrote:
Paul Jackson wrote:
In the overall kernel (Linus's bk tree) I count:
733 lines matching 'for *( *; *; *)'
718 lines matching 'while *( *1 *)'
In the kernel/*.c files, I count 15 of the 'for(;;)' sty
On Tue, Mar 15, 2005 at 03:50:26PM +, Phillip Lougher wrote:
> Paul Jackson wrote:
> >In the overall kernel (Linus's bk tree) I count:
> >
> > 733 lines matching 'for *( *; *; *)'
> > 718 lines matching 'while *( *1 *)'
> >
> >In the kernel/*.c files, I count 15 of the 'for(;;)' style a
Paul Jackson wrote:
In the overall kernel (Linus's bk tree) I count:
733 lines matching 'for *( *; *; *)'
718 lines matching 'while *( *1 *)'
In the kernel/*.c files, I count 15 of the 'for(;;)' style and 1 of the
'while(1)' style.
Certainly the 'for(;;)' style is acceptable, and ev
In the overall kernel (Linus's bk tree) I count:
733 lines matching 'for *( *; *; *)'
718 lines matching 'while *( *1 *)'
In the kernel/*.c files, I count 15 of the 'for(;;)' style and 1 of the
'while(1)' style.
Certainly the 'for(;;)' style is acceptable, and even slightly to
su
On Tue, Mar 15, 2005 at 12:47:23PM +1100, Nick Piggin wrote:
> Matt Mackall wrote:
>
> >>+ for (;;) {
> >
> >while (1)
>
> I always thought for (;;) was preferred. Or at least acceptable?
The for (;;) form has always struck me as needlessly clever and I've
known it to puzzle coworkers. I try t
Matt Mackall wrote:
+ for (;;) {
while (1)
I always thought for (;;) was preferred. Or at least acceptable?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.h
Phillip Lougher <[EMAIL PROTECTED]> wrote:
>
> Please apply the following two patches which adds SquashFS to the
> kernel.
> +
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
> +#include
>
A quick skim...
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
> + *
> + * inode.c
> + */
> +
> +#include
> +#include
> +#include
Andrew, Greg,
Please apply the following two patches which adds SquashFS to the
kernel. SquashFS is self contained compressed filesystem, and it
has been used by a large amount of projects over the last few years
without problems.
A number of people have started to ask me to submit it to the kerne
19 matches
Mail list logo
