Ferenc Havasi | 17 Aug 15:59
Picon
Favicon

JFFS2 (NAND) mount time improvment

Dear All,

Is here someone, who is interested in $SUBJECT and have a NAND device 
and some time to help us to test? Please contact me!

Now we have some patches (the idea is that one was discussed with David 
at http://lists.infradead.org/pipermail/linux-mtd/2004-June/009873.html ).

These are tested with mtdram and works, but unfortunatelly we don't have 
any NAND device yet to test and measure its effect on mount time 
(certainly, it should be faster).

Regards,
Ferenc

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

David Woodhouse | 17 Aug 16:09
Favicon

Re: JFFS2 (NAND) mount time improvment

On Tue, 2004-08-17 at 15:59 +0200, Ferenc Havasi wrote:
> Now we have some patches (the idea is that one was discussed with David 
> at http://lists.infradead.org/pipermail/linux-mtd/2004-June/009873.html ).

Please just send them to the list. I'm sure some eager testers will
crawl out of the woodwork :)

How did you handle nlink? I'm sure I had a cunning plan for it at one
point but I couldn't remember it at time I composed the message you're
looking at, so I was hand-waving. 

--

-- 
dwmw2

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

maskman | 17 Aug 16:42

Porting JFFS2 with NAND to ECOS

Hi,

I will port JFFS2's uptodated version to ECOS2.0. As I know, ECOS don't support NAND. But I need NAND file system.

What different points is between ECOS JFFS2 ans current JFFS2 version, in the view point of internal
machanisim of JFFS2. Also, What is critical things, or time-consumming stuff in my porting job?

Thanks in advance.

Maskman

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com

Ferenc Havasi | 18 Aug 23:37
Picon
Favicon

Re: JFFS2 (NAND) mount time improvment

David Woodhouse wrote:
> Please just send them to the list. I'm sure some eager testers will
> crawl out of the woodwork :)

OK, I've planned to do it - just needed some time to make them more 
presentable :)

> How did you handle nlink? I'm sure I had a cunning plan for it at one
> point but I couldn't remember it at time I composed the message you're
> looking at, so I was hand-waving. 

We tried to modify only jffs2_scan_eraseblock to read less NAND page 
than before.

There will be a JFFS2_NODETYPE_INODE_CACHE node at the end of every 
erase block if you run mkfs.jffs2 using its -C option. (there is an 
other new option: -N to specify the size of the nand page)

In this new node there is a record for every node stored in the erase 
block. Every neccesary node-info is stored except the infos of 
JFFS2_NODETYPE_DIRENT nodes. Now we stores only their offsets and have 
to read them - certainly it can cause some slow-down :(

As I wrote we didn't test is on NAND - we can just hope the best. It is 
tested yet only with kernel 2.6.8.1 with mtd snapshot 2004-08-17 using 
mtdram.

Michael Howard wrote:
 > I have a 256M Samsung Nand and really need this reduced mount time.  I
 > would be most willing to test out your improvements.   Pls let me know
(Continue reading)

Jeroen | 23 Aug 11:10
Picon

Only two 8 kbyte FLASH NOR blocks, is this enough for FFS2?

Hi.

I only have two 8 kbyteFLASH  NOR blocks free. I only need to write a 
few very small setting files on it. Are two 8 kbyte blocks enough for 
making a FFS system? I don't want to erase a block every time a file 
(500 bytes) is written. Should I take a look at an other system to store 
my settings?

Regards,

Jeroen

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com

David Woodhouse | 23 Aug 12:19
Favicon

Re: Only two 8 kbyte FLASH NOR blocks, is this enough for FFS2?

On Mon, 2004-08-23 at 11:10 +0200, Jeroen wrote:
> Hi.
> 
> I only have two 8 kbyteFLASH  NOR blocks free. I only need to write a 
> few very small setting files on it. Are two 8 kbyte blocks enough for 
> making a FFS system? I don't want to erase a block every time a file 
> (500 bytes) is written. Should I take a look at an other system to store 
> my settings?

Theoretically, yes. You can write 16 updates sequentially to each block,
each update marking the previous one as obsolete. Then when you write
the first update to the second block, you can erase the first block.

JFFS2 doesn't currently handle that automatically -- you need to tweak
the free block thresholds in jffs2_calc_trigger_levels() in build.c, at
the very least.

--

-- 
dwmw2

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo <at> axis.com


Gmane