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

Artem B. Bityuckiy wrote:
> 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.

I undersand you, but unfortunatelly now there is no way to change 
compression mode dimamically. There was (using procfs) but when David 
tried to commit it to the kernel, someone (I don't remember who but one 
of the kernel developers) declared it bad.

David asked me to reimplement it is sysfs, but that is not an easy 
thing. Not technically. There is no fs subdirectory in sysfs. I read in 
the mailling list archive of linux-fsdevel@vger.kernel.org. Someone 
tried to submit a patch to make this fs subdirectory, because he need it 
for NFS. The answer declared it as very bad, too... (sysfs has a 
different philosopy...) I had some private discussion with the patch 
submitter (what happened exactly, what was really the problem,... what 
is his plan). He wrote that he try it again later. He think the guy who 
declared his patch bad really hates sysfs (and procfs too). So I decided 
to wait, too. :(

But this new "compressoin configuration" concept may cause that we don't 
need sysfs/procfs.

Bye,
Ferenc

  reply	other threads:[~2004-10-19 12:03 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
2004-10-19 12:06             ` Ferenc Havasi [this message]
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=4175035B.80101@inf.u-szeged.hu \
    --to=havasi@inf.u-szeged.hu \
    --cc=abityuckiy@yandex.ru \
    --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