All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: benson_young@sercomm.com
Cc: Benson Young <benson6877@gmail.com>,
	linux-mtd@lists.infradead.org,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: Fwd: Encrypted NAND flash over UBI performance bench marking
Date: Fri, 22 Apr 2016 14:43:52 +0200	[thread overview]
Message-ID: <571A1C88.505@nod.at> (raw)
In-Reply-To: <OFC23048C2.C6508474-ON48257F9D.003136DE-48257F9D.00338EFE@sercomm.com>

Am 22.04.2016 um 11:23 schrieb benson_young@sercomm.com:
> Hi Richard,
> 
> If my applications within the EXT4 rootfs do not write on a very regular basis, and setting noatimein
> mount option. will I still have NAND thrashing problem? i.e. the file system itself will try to
> update/journal/sync on a very regular basis (something like 30 second buffer flush)? As you can see
> my knowledge with EXT4 and most file systems are very limited.

You mean ext4 on top of a loopback file on UBIFS?
I don't think it will be a big problem. But to be sure do some tests. :-)
UBI exports ec counter stats in sysfs.

Thanks,
//richard

      parent reply	other threads:[~2016-04-22 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABJ+KKvj4VDUvqTnj+dWf8+qzhK5hhvacdx551JbzmUQye4biA@mail.gmail.com>
2016-04-22  8:40 ` Encrypted NAND flash over UBI performance bench marking Richard Weinberger
     [not found]   ` <CABJ+KKvaVX9HMtFYjOnOwW1xHxw5v9ecZs+SFdJYsCmtLNOKiw@mail.gmail.com>
     [not found]     ` <OFC23048C2.C6508474-ON48257F9D.003136DE-48257F9D.00338EFE@sercomm.com>
2016-04-22 12:43       ` Richard Weinberger [this message]

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=571A1C88.505@nod.at \
    --to=richard@nod.at \
    --cc=benson6877@gmail.com \
    --cc=benson_young@sercomm.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.