public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: Ferenc Havasi <havasi@inf.u-szeged.hu>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 compression
Date: Tue, 19 Oct 2004 14:48:19 +0400	[thread overview]
Message-ID: <4174F0F3.7030604@yandex.ru> (raw)
In-Reply-To: <4174E7D3.9050706@inf.u-szeged.hu>

Ferenc Havasi wrote:
> Now the compression mode is a global thing. It can be configured by 
> kernelconfig and is the same for every filesystem. There is no reserved 
> space to store it in the different JFFS2 filesystems (it should need a 
> new type of node or something like that).
It isn't needed to store the default compression mode *on flash*. If you 
just move the variable jffs2_compression mode to the jffs2_sb_info 
structure, you will have per-filesystems compression mode. This means, 
for example, that if user changes (dynamically) the compression mode for 
one file-system, the compression mode for another file system isn't changed.

> 
> There is plans for the future. One of them: there will be "compression 
> configurations". This is much more general thing than compression mode. 
> (contais not only the compression mode but the set of the enabled 
> compressors and its priority) The user will be able to define different 
> compressor configuration for files or directories. The description of 
> these configuration will be stored in a new type of node 
> (RWCOMPACT_COPY), and the index of the requested configuration will be 
> stored in the upper 4 bits of 'usercompr' field of jffs2_raw_inode.
Great idea!

But this is the another (deeper) layer. If a file/directory has the 
compression mode set, it would be applied. But the *per-filesystem* 
compression may be used by default (for those files who are not 
mentioned in your "compression configuration" node).



-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

  parent reply	other threads:[~2004-10-19 10:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16 17:14 JFFS2 bugfix Artem B. Bityuckiy
2004-10-18 11:57 ` Ferenc Havasi
2004-10-18 12:16   ` Artem B. Bityuckiy
2004-10-19  7:57     ` Ferenc Havasi
2004-10-19  8:06       ` Artem B. Bityuckiy
2004-10-19  9:16       ` David Woodhouse
     [not found]       ` <4174D508.8050508@yandex.ru>
2004-10-19 10:09         ` JFFS2 compression Ferenc Havasi
2004-10-19 10:14           ` David Woodhouse
2004-10-20  9:16             ` Ferenc Havasi
2004-10-20  9:16               ` David Woodhouse
2004-10-20 11:13               ` Artem B. Bityuckiy
2004-10-20 11:53                 ` Ferenc Havasi
2004-10-20 12:06                   ` Artem B. Bityuckiy
2004-10-19 10:48           ` Artem B. Bityuckiy [this message]
2004-10-19 12:06             ` Ferenc Havasi
2004-10-19 12:19               ` Artem B. Bityuckiy
2004-10-19 13:43                 ` David Woodhouse
2004-10-19 14:07                   ` Ferenc Havasi
2004-10-19 14:08                     ` David Woodhouse

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=4174F0F3.7030604@yandex.ru \
    --to=abityuckiy@yandex.ru \
    --cc=havasi@inf.u-szeged.hu \
    --cc=linux-mtd@lists.infradead.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