From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Tanya Brokhman <tlinder@codeaurora.org>,
linux-mtd@lists.infradead.org, linux-arm-msm@vger.kernel.org,
jlauruhn@micron.com
Subject: Re: [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling
Date: Wed, 12 Nov 2014 14:07:43 +0200 [thread overview]
Message-ID: <1415794063.22887.245.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <54628207.5030205@nod.at>
On Tue, 2014-11-11 at 22:39 +0100, Richard Weinberger wrote:
> Please don't (ab)use fastmap. If you really need persistent read-counters use an internal UBI volume.
Just like you, I do not think the proposed solution is the right answer
to the problem, at least so far. But if we imagine that Tanya proves
that the counters is the right thing, storing them in fastmap would be
the first thing which comes to mind. Just calling this an abuse without
explaining (even if this is right) is not very collaborative.
Let me see why would that be an "abuse"... Probably because of the
nature of the data. Fastmap contains data which only changes in case of
writes (well, more precisely, erases, but those usually go are related
to writes). Read counters are completely opposite - they stay constant
when we write and change when we read.
Putting them all to the same on-flash area is possible, but is it
optimal? I wouldn't be so sure, I see cons. and pros.
Any other reasons?
Artem.
next prev parent reply other threads:[~2014-11-12 12:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 13:49 [RFC/PATCH 0/5 v2] mtd:ubi: Read disturb and Data retention handling Tanya Brokhman
2014-10-26 20:39 ` Richard Weinberger
2014-10-27 8:41 ` Tanya Brokhman
2014-10-27 8:56 ` Richard Weinberger
2014-10-29 11:03 ` Tanya Brokhman
2014-10-29 12:00 ` Richard Weinberger
2014-10-31 13:12 ` Tanya Brokhman
2014-10-31 15:34 ` Richard Weinberger
2014-10-31 15:39 ` Richard Weinberger
2014-10-31 22:55 ` Jeff Lauruhn (jlauruhn)
[not found] ` <54563211.6070409@codeaurora.org>
2014-11-07 9:21 ` Artem Bityutskiy
2014-11-02 13:25 ` Tanya Brokhman
2014-11-06 8:07 ` Artem Bityutskiy
[not found] ` <545B66BA.4090904@codeaurora.org>
[not found] ` <1415350722.958.286.camel@sauron.fi.intel.com>
2014-11-11 20:36 ` Tanya Brokhman
2014-11-11 21:39 ` Richard Weinberger
2014-11-12 12:07 ` Artem Bityutskiy [this message]
2014-11-12 13:01 ` Richard Weinberger
2014-11-12 13:32 ` Artem Bityutskiy
2014-11-12 15:37 ` Richard Weinberger
2014-11-12 11:55 ` Artem Bityutskiy
2014-11-13 12:13 ` Tanya Brokhman
2014-11-13 13:36 ` Artem Bityutskiy
2014-11-23 8:13 ` Tanya Brokhman
2014-11-02 13:23 ` Tanya Brokhman
2014-11-02 13:54 ` Richard Weinberger
2014-11-02 14:12 ` Tanya Brokhman
2014-11-02 17:02 ` Richard Weinberger
2014-11-02 17:18 ` Tanya Brokhman
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=1415794063.22887.245.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=jlauruhn@micron.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tlinder@codeaurora.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