public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Anatolij Gustschin <agust@denx.de>,
	Holger Brunck <holger.brunck@keymile.com>,
	Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: [PATCH 0/7] UBIFS: fix recovery on CFI NOR
Date: Wed,  2 Feb 2011 10:21:51 +0200	[thread overview]
Message-ID: <1296634917-19335-1-git-send-email-dedekind1@gmail.com> (raw)

From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>

Hi,

here is the patch-set against the latest Linux kernel (e.g. 2.6.38-rc3)
which should fix CFI NOR flash recovery.

The previous attempt was not entirely successful - it broke backward
compatibility and was reverted:

http://marc.info/?l=linux-kernel&m=129631939419818&w=2

This patch-set goes the following way:
1. Incorporates the notion of 'writebufsize' into UBI and UBIFS as
   'max_write_size', because using term write-buffer would be confusing, as
   UBIFS has its own write-buffers.
2. Changes UBIFS write-buffer and makes it of 'max_write_size', instead of
   'min_io_size'. This presumably leads to better performance because we
   accumulate more data and write them in larger chunks and faster.
   And we do not waste space when synchronizing UBIFS write-buffers because we
   write only the used amount of bytes aligned to 'min_io_size'. So this is an
   improvement.
3. Tweak UBIFS recovery and make it aware of the fact that we can write in
   chunks larger than 'min_io_size'. Namely, we can write in 'max_write_size'
   chunks.

Could you guys please test this WRT power cuts and let me know if it solves the
issues?

Note, obviously this requires patches from Anatolij which introduce
'writebufsize' to MTD, except of the UBI patch which was reverted later.

Artem.

             reply	other threads:[~2011-02-02  8:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02  8:21 Artem Bityutskiy [this message]
2011-02-02  8:21 ` [PATCH 1/7] UBI: incorporate maximum write size Artem Bityutskiy
2011-02-02  8:21 ` [PATCH 2/7] UBIFS: " Artem Bityutskiy
2011-02-02  8:21 ` [PATCH 3/7] UBIFS: introduce write-buffer size field Artem Bityutskiy
2011-02-02  8:21 ` [PATCH 4/7] UBIFS: use max_write_size for write-buffers Artem Bityutskiy
2011-02-02  8:21 ` [PATCH 6/7] UBIFS: amend commentaries in io.c to match new situation Artem Bityutskiy
2011-02-02  8:21 ` [PATCH 7/7] UBIFS: use max_write_size during recovery Artem Bityutskiy
2011-02-02 12:48 ` [PATCH 0/7] UBIFS: fix recovery on CFI NOR Anatolij Gustschin
2011-02-02 15:21 ` Holger Brunck
2011-02-02 17:16   ` Artem Bityutskiy
2011-02-03  9:01     ` Holger Brunck

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=1296634917-19335-1-git-send-email-dedekind1@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=agust@denx.de \
    --cc=holger.brunck@keymile.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nvbolhuis@aimvalley.nl \
    /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