public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Another compiler error: sumtool.c
Date: Thu, 22 Sep 2005 10:50:33 +0400	[thread overview]
Message-ID: <43325439.1060307@yandex.ru> (raw)
In-Reply-To: <20050922064104.GM8421@lunn.ch>

Andrew Lunn wrote:
> Could you define small.
No, I cannot. This must be found out experimentally. I just warned you 
about possible EBS effect.

> I will be checking this anyway. I need to improve the mount time
> performance of eCos's version of JFFS2. For the system i'm working on
> now the eCos redboot loader has JFFS2 from CVS from a year or so
> ago. It takes four or five times longer to mount the filesystem than
> the JFFS2 code in the Linux 2.4.x version of the kernel redboot is
> booting. For the particular application this device is being used in i
> need very fast boot times and currently the RedBoot JFFS2 mount is the
> bottleneck. So i was hopeing that bringing JFFS2 up to date in eCos's
> Redboot and adding EBS might match the performance of the old 2.4.x
> code. Testing will soon tell.

EBS makes mount really faster. But then the JFFS2 checker is working, 
and in case of NOR+EBS it will work longer and eat more CPU. JFFS2 
writers are blocked while the checker is working, so it may slow down 
the boot process. That's the theory, experiments are needed.


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

  reply	other threads:[~2005-09-22  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21 21:13 Another compiler error: sumtool.c Andrew Lunn
2005-09-22  6:20 ` Artem B. Bityutskiy
2005-09-22  6:41   ` Andrew Lunn
2005-09-22  6:50     ` Artem B. Bityutskiy [this message]
2005-09-22  9:40       ` Ferenc Havasi
2005-09-22  9:50         ` Artem B. Bityutskiy

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=43325439.1060307@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=andrew@lunn.ch \
    --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