All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Yanok <yanok@emcraft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/RFC] Some speed improvements to U-Boot JFFS2 code
Date: Sat, 01 Nov 2008 04:00:26 +0300	[thread overview]
Message-ID: <490BAA2A.6020806@emcraft.com> (raw)
In-Reply-To: <48F73540.3020504@gmx.de>

Hello Michael,

Michael Lawnick wrote:
> I have put these patches to our board (MPC8548, NOR Flash, MTD partition
> size 48MB).
>
> a) performance has improved (execution time of 'ls' reduced from ~16s to
> ~1.5s)
>   

Sounds good. That is what we were expecting.

> b) there is a bug in the patch
> 0005-jffs2-add-buffer-to-cache-flash-accesses:
> The passage
>
> @@ -724,12 +731,14 @@ jffs2_1pass_read_inode(struct b_lists *pL, u32
> inode, char *dest)
>  				latestVersion = jNode->version;
>  			}
>  		}
> -		put_fl_mem(jNode);
> +		if (pL->readbuf == NULL)
> +			put_fl_mem(jNode);
>  	}
>  #endif
>
> should be
>
> @@ -724,12 +731,14 @@ jffs2_1pass_read_inode(struct b_lists *pL, u32
> inode, char *dest)
>  				latestVersion = jNode->version;
>  			}
>  		}
> -		put_fl_mem(jNode);
> +		if (pL->readbuf == NULL)
> +			put_fl_mem(jNode, NULL);
>  	}
>  #endif
>   

You are right. We haven't just tried to use CFG_JFFS2_SORT_FRAGMENTS...

> c) I found no improvement with CFG_JFFS2_SORT_FRAGMENTS set (the way I
> detected b) ;-)
>   

Same as above... We don't use CFG_JFFS2_SORT_FRAGMENTS... But it's very
sad result really... I have no idea what is wrong with it...

> d) output of 'ls' is corrupted: no date and access right output,
> directories in / are shown multiple times

Can you please be more specific on this? Is this with
CFG_JFFS2_SORT_FRAGMENTS enabled or not? How did you create your FS? I
can't reproduce any of described symptoms on our system...

The only thing I can tell you for now is that the first patch from my
posting is wrong, the following patch fixes the problem:

  reply	other threads:[~2008-11-01  1:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13  5:53 [U-Boot] [PATCH/RFC] Some speed improvements to U-Boot JFFS2 code Ilya Yanok
2008-10-13  5:53 ` [U-Boot] [PATCH] jffs2: add sector_size field to part_info structure Ilya Yanok
2008-10-13  8:17   ` Wolfgang Denk
2008-10-15 12:35     ` Ilya Yanok
2008-10-13  5:53 ` [U-Boot] [PATCH] jffs2: rewrite jffs2 scanning code based on Linux one Ilya Yanok
2008-10-13  5:53 ` [U-Boot] [PATCH] jffs2: summary support Ilya Yanok
2008-10-13  5:53 ` [U-Boot] [PATCH] jffs2: fix searching for latest version in jffs2_1pass_list_inodes() Ilya Yanok
2008-10-13  5:53 ` [U-Boot] [PATCH] jffs2: add buffer to cache flash accesses Ilya Yanok
2008-10-13  5:53 ` [U-Boot] [PATCH] jffs2: cache data_crc results Ilya Yanok
2008-10-14  9:25   ` Michael Lawnick
2008-10-13  8:14 ` [U-Boot] [PATCH/RFC] Some speed improvements to U-Boot JFFS2 code Wolfgang Denk
2008-10-15 12:44   ` Ilya Yanok
2008-10-16 12:36     ` Michael Lawnick
2008-11-01  1:00       ` Ilya Yanok [this message]
2008-11-02 16:02         ` Wolfgang Denk
2008-11-02 19:08           ` Ilya Yanok
2008-11-04 11:14         ` Michael Lawnick
2008-11-04 12:31           ` Michael Lawnick
2008-11-04 13:14             ` Joakim Tjernlund
2008-11-05  7:59               ` Michael Lawnick
2008-11-11  6:49             ` Alexey Neyman
2008-11-11  8:19               ` Joakim Tjernlund

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=490BAA2A.6020806@emcraft.com \
    --to=yanok@emcraft.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.