public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: Konstantin Kletschke <lists@ku-gbr.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 with sync burst mode
Date: Fri, 11 Mar 2005 14:59:36 +0300	[thread overview]
Message-ID: <42318828.9030806@yandex.ru> (raw)
In-Reply-To: <20050311112730.GC11203@synertronixx3>

Konstantin Kletschke wrote:
> But is moving the memcpy function a valid fix? There must be something
> really wrong which should be fixed :/ DCache corruption i.e. missing
> invalidating at the right time?
Err, how can ti be valid? Do you see any problem in JFFS2 itself?

AFAIU, you have problems in layers which are bellow JFFS2. JFFS2 itself 
is correct. Your fix in JFFS2 is not actually fix, you have just hidden 
your problem, right?

Unfortunately, I can't help you with your Dcache problems. In fact, I 
have very limited NOR experience for now, and I might help if you find 
bugs in JFFS2, not in underlying drivers. May be anybody else...


> But if I understood correct the not created-cleanmarkers-by-bootloader
> problem is "solved" on second boot? I see this here also, the 1st mount
> takes ages, the following are fast.
This depends on how long have you used JFFS2 after the first mount. 
Blocks aren't erased immediately on mount. Instead, this work is done 
later. So, *some* blocks *might* stay not re-erased.

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

  reply	other threads:[~2005-03-11 12:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 10:44 jffs2 with sync burst mode Konstantin Kletschke
2005-03-11 11:15 ` Artem B. Bityuckiy
2005-03-11 11:27   ` Konstantin Kletschke
2005-03-11 11:59     ` Artem B. Bityuckiy [this message]
2005-03-11 11:57 ` Konstantin Kletschke
  -- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:14 Konstantin Kletschke
2005-03-10 13:15 ` Artem B. Bityuckiy
2005-03-10 15:22   ` Konstantin Kletschke
2005-03-10 15:54     ` Artem B. Bityuckiy
2005-03-10 16:40       ` Konstantin Kletschke
2005-03-10 19:25         ` Steve Wahl
2005-03-10 23:24           ` Konstantin Kletschke
2005-03-10 15:46   ` Konstantin Kletschke
2005-03-10 16:21     ` Artem B. Bityuckiy
2005-03-10 16:48       ` Konstantin Kletschke
2005-03-10 17:08         ` Artem B. Bityuckiy
     [not found]         ` <JPEALJAFNGDDLOPNDIEECEJFDBAA.joakim.tjernlund@lumentis.se>
2005-03-10 23:18           ` Konstantin Kletschke
     [not found]             ` <BCEFJBPJCGFCNMMMIDBHEEPKCKAA.Joakim.Tjernlund@lumentis.se>
2005-03-11  0:03               ` Konstantin Kletschke
2005-03-10 17:02       ` Konstantin Kletschke
2005-03-10 17:17         ` Artem B. Bityuckiy
2005-03-10 18:27           ` Konstantin Kletschke
2005-03-10 18:53           ` Konstantin Kletschke

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=42318828.9030806@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lists@ku-gbr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox