From: Artem Bityutskiy <dedekind1@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Tanya Brokhman <tlinder@codeaurora.org>,
dedeking1@gmail.com, linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC/PATCH 1/5] mtd: ubi: Read disturb infrastructure
Date: Fri, 03 Oct 2014 18:38:25 +0300 [thread overview]
Message-ID: <1412350705.3795.105.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <542D5BC0.5040207@nod.at>
On Thu, 2014-10-02 at 16:05 +0200, Richard Weinberger wrote:
> The question is, do we really need all this values on-flash?
Good question, this is why I requested some kind of design description,
which would clearly explain the problem.
Just off-the top of my head, may be it could be enough to keep the
counters only in the UBI headers, may be it is enough to work with some
kind of averages. But it is hard to tell without clearly understanding
the problem we are solving.
next prev parent reply other threads:[~2014-10-03 15:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 6:37 [RFC/PATCH 1/5] mtd: ubi: Read disturb infrastructure Tanya Brokhman
2014-09-28 8:18 ` Richard Weinberger
2014-09-28 8:48 ` Tanya Brokhman
2014-09-28 8:54 ` Richard Weinberger
2014-09-28 10:46 ` Tanya Brokhman
2014-09-28 10:54 ` Richard Weinberger
2014-10-02 12:50 ` Tanya Brokhman
2014-10-02 13:24 ` Richard Weinberger
2014-10-02 13:42 ` Tanya Brokhman
2014-10-02 14:05 ` Richard Weinberger
2014-10-03 15:38 ` Artem Bityutskiy [this message]
2014-10-07 13:55 ` Richard Weinberger
2014-10-02 13:36 ` Richard Weinberger
2014-10-02 14:11 ` Tanya Brokhman
2014-09-28 12:11 ` Artem Bityutskiy
2014-09-28 14:54 ` 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=1412350705.3795.105.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dedeking1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).