public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: dedekind@infradead.org
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH/RFC] reserved pool
Date: Wed, 17 May 2006 00:30:21 +0100	[thread overview]
Message-ID: <1147822221.30771.6.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1147702746.20604.10.camel@sauron.oktetlabs.ru>

On Mon, 2006-05-15 at 18:19 +0400, Artem B. Bityutskiy wrote:
> On Sun, 2006-05-14 at 20:39 +0100, David Woodhouse wrote:
> > > Then go and bug dwmw2 about merging it. ;) 
> > 
> > We talked about changing the way the reserved size is actually handled
> > in the allocation routine.... did a new version ever show up?
> > 
> Please,
> 
> look/pull the '[JFFS2] add reserved pool feature' patch from
> http://git.infradead.org/?p=users/dedekind/dedekind-mtd-2.6.git;a=summary

I cleaned it up so it looks like this.... and then decided not to apply
it. I don't like this kind of thing being a mount option. Make a new
node type for 'filesystem options'. Make it an RWCOMPAT_COPY node type.
Store the reserved size in it and do it through an ioctl like chattr
does on ext2 -- and make mkfs.jffs2 write it too. 

We'll want compression types stored in that node type too, I suspect.

-- 
dwmw2

  reply	other threads:[~2006-05-16 23:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 12:45 [PATCH/RFC] reserved pool Artem B. Bityutskiy
2006-05-10  8:29 ` Artem B. Bityutskiy
2006-05-10 13:35   ` Jörn Engel
2006-05-10 13:54     ` Artem B. Bityutskiy
2006-05-10 13:58       ` Jörn Engel
2006-05-14 19:39         ` David Woodhouse
2006-05-15 14:19           ` Artem B. Bityutskiy
2006-05-16 23:30             ` David Woodhouse [this message]
2006-05-16 23:31               ` David Woodhouse
2006-05-17  6:49               ` Artem B. Bityutskiy
2006-05-17  9:19                 ` 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=1147822221.30771.6.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=dedekind@infradead.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --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