public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: xiaochuanxv <xiaochuanxv@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: about the _dtype_ parameter
Date: Wed, 14 Jan 2009 14:48:39 +0200	[thread overview]
Message-ID: <1231937319.5973.67.camel@localhost.localdomain> (raw)
In-Reply-To: <1231952548.3615.66.camel@localhost.localdomain>

On Thu, 2009-01-15 at 01:02 +0800, xiaochuanxv wrote:
> Sorry, a mistake in writing: 
> 
> (Suppose wr-ratio represent the ratio of erasures due to wear-leveling
> to erasure total physical erase-block erasures. )
> I found that when most of the @dtype is equal to UBI_SHORTTERM, the
> wr-ratio is approximately equal to 0.1%, whereas is greater than
>  
> 0.4% 
> 
> when @dtype is always UBI_UNKNOWN. It seem that the data type call-back
> policy does NOT make any sense in the current implementation.

Hmm, interesting observation. I would suggest you to add statistics
support to UBI. Introduce a counter for the amount of times UBI moves
PEB data, and expose it via sysfs. You may probably add other counters
like number of erasures and so on.

Then it will be easier to do testing and investigations.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2009-01-14 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ff5b6bcd0901050659k4679c64egffcfa054da4c9034@mail.gmail.com>
2009-01-05 15:14 ` about the _dtype_ parameter Artem Bityutskiy
2009-01-12  9:26   ` xiaochuan-xu
2009-01-13  9:41     ` Artem Bityutskiy
2009-01-14 16:37       ` xiaochuanxv
2009-01-14 17:02       ` xiaochuanxv
2009-01-14 12:48         ` Artem Bityutskiy [this message]
     [not found] <TWMHGPGDBZQLPDUUCZBAWZYAUCWM.20061402067@cqu.edu.cn>
2009-01-05 13:15 ` Artem Bityutskiy

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=1231937319.5973.67.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=xiaochuanxv@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