From: Artem Bityutskiy <dedekind@infradead.org>
To: Gregory CLEMENT <gclement00@gmail.com>
Cc: Joern Engel <joern@logfs.org>,
linux-mtd@lists.infradead.org,
Konstantin Baydarov <kbaidarov@dev.rtsoft.ru>,
Vitaly Wool <vitalywool@gmail.com>
Subject: Re: [PATCH] [MTD] ROMBLOCK: Readonly Block Device Layer Over MTD
Date: Sun, 16 Dec 2007 14:45:40 +0200 [thread overview]
Message-ID: <1197809140.25999.63.camel@sauron> (raw)
In-Reply-To: <47651028.5030506@gmail.com>
On Sun, 2007-12-16 at 12:46 +0100, Gregory CLEMENT wrote:
> I send this mail again as my previous patch was mangled, I hope that now
> I fixed it.
>
> Hi,
> I generated this patch for linux 2.6.24.rc5 and tested it with cramfs
> and squashfs file systems.
> As Konstantin Baydarov submit this patch first maybe it would be better
> than he sign this patch, but if he can't or don't want it, I don't mind
> sign it...
>
> >From 9a06e0c1818e4b27a04a8adac7eee551c8aac115 Mon Sep 17 00:00:00 2001
> From: Gregory CLEMENT <gclement00@gmail.com>
> Date: Wed, 12 Dec 2007 17:41:23 +0100
> Subject: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD
>
> Description:
> The following patch adds readonly block device layer over mtd
> that allows to use any filesystem on this device in RO mode and thus
> gain faster mount times and better throughput rates.
> It allows to put one RO filesystem into NAND using a bad-block aware
> program initially, and mount it. But be aware, it doesn't handle run-
> time bit flips or errors (even if this event seems pretty rare).
>
> How it works:
> Blocks translation routine was added to read sector function. Assuming
> that bad block won't appear during MTD reading and BBT is correct, bad
> block is skipped and requested block is lazily mapped to good one.
> Block driver based on the mtd readonly device driver mtdblock_ro.c and
> translation routine was taken from the patch of Pantelis Antoniou
> (which can be found at
> http://lists.infradead.org/pipermail/linux-mtd/2004-May/009672.html).
> This patch was originally submit by Konstantin Baydarov, but never
> included nor rejected ( see
> http://lists.infradead.org/pipermail/linux-mtd/2006-November/016835.html).
>
> Signed-off-by: Gregory CLEMENT <gclement00@gmail.com>
For me this amount of mtdblock drivers looks strange. We have 2 already,
and this is the third.
If you really cannot modify mtdblock_ro, then I'd kindly ask you to also
write a good explanation: what are all those mtdblock/rombolck, what is
the difference, why we need so many of them. Then I would put your text
to the MTD web site.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2007-12-16 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 11:46 [PATCH] [MTD] ROMBLOCK: Readonly Block Device Layer Over MTD Gregory CLEMENT
2007-12-16 12:45 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-13 7:32 Gregory CLEMENT
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=1197809140.25999.63.camel@sauron \
--to=dedekind@infradead.org \
--cc=gclement00@gmail.com \
--cc=joern@logfs.org \
--cc=kbaidarov@dev.rtsoft.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=vitalywool@gmail.com \
/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