From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'David Woodhouse'" <dwmw2@infradead.org>
Cc: 'Linux MTD mailing list' <linux-mtd@lists.infradead.org>
Subject: RE: sync() takes minutes while erasing
Date: Thu, 28 Jun 2007 20:59:51 +0200 [thread overview]
Message-ID: <001901c7b9b6$81e76340$0e67a8c0@Jocke> (raw)
In-Reply-To: <1183056861.1170.191.camel@pmac.infradead.org>
> -----Original Message-----
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: den 28 juni 2007 20:54
> To: joakim.tjernlund@transmode.se
> Cc: Linux MTD mailing list
> Subject: Re: sync() takes minutes while erasing
>
> On Wed, 2007-06-20 at 16:49 +0200, Joakim Tjernlund wrote:
> > Ok, found the cause:
> > jffs2_erase_pending_blocks(c, 0) is called from
> > jffs2_write_super() and it hangs until all
> > pending erases are complete.
> >
> > Why do jffs2_write_super() need to call
> > jffs2_erase_pending_blocks(c, 0)? Seems like a bad idea to me.
>
> It's because pdflush is the best context I could find for
> actually doing
> the erases we need. But now I think we can use pdflush_operation()
> instead of having to do it from write_super(), so maybe we can fix the
> thing that offends you.
Thanks, this stop the complaints from the test team. They
don't like to wait a few mins every time they delete an old install
and reboot.
Jocke
next prev parent reply other threads:[~2007-06-28 19:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 14:21 sync() takes minutes while erasing Joakim Tjernlund
2007-06-20 14:49 ` Joakim Tjernlund
2007-06-20 16:09 ` Josh Boyer
2007-06-20 16:26 ` Joakim Tjernlund
2007-06-20 16:29 ` Jörn Engel
2007-06-20 16:45 ` Joakim Tjernlund
2007-06-20 16:59 ` Josh Boyer
2007-06-28 18:54 ` David Woodhouse
2007-06-28 18:59 ` Joakim Tjernlund [this message]
2007-06-28 19:02 ` David Woodhouse
2007-07-02 12:58 ` Joakim Tjernlund
2007-08-06 16:18 ` Joakim Tjernlund
2007-08-08 13:06 ` Joakim Tjernlund
2007-11-08 16:37 ` Joakim Tjernlund
2007-11-08 17:20 ` 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='001901c7b9b6$81e76340$0e67a8c0@Jocke' \
--to=joakim.tjernlund@transmode.se \
--cc=dwmw2@infradead.org \
--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