From: gianluca <gianlucarenzi-RMR/+jklkADqD7ZJT3/+rDUZDU+1vuVT@public.gmane.org>
To: Clemens Eisserer
<linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Hello list!
Date: Wed, 12 Feb 2014 15:16:12 +0100 [thread overview]
Message-ID: <52FB822C.1060208@eurekelettronica.it> (raw)
In-Reply-To: <CAFvQSYTuM7Zjfz47UGU3KnTgH1iSRWiiZ3iSqXUiu7MKFnOmFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 02/12/2014 02:04 PM, Clemens Eisserer wrote:
> Hi Gianluca,
>
>> What about the wear-leveling of this configuration of the eMMC device?
>
> Actually nilfs2 is by design as friendly to flash devices with a weak
> controller as possible.
> It only performs sequential writes, yielding a perfectly equal
> distribution of writes across the device.
> Nilfs2 even overwrites static data which won't be written to when
> using other filesystems - which is great for devices supporting only
> dynamic wear leveling (usually SD, mmc, emmc, ...).
>
Ok. good news to me.
> However, there is one issue left - the (two) superblocks are written
> to periodically in short intervals.
> There is currently an ongoing discussion about this and Andreas has
> posted an experimental patch which works well on my raspberry pi.
>
What patch? Can you give some additional info? I am running kernel
3.12.2 vanilla.
>> Can you point me on some tools, utilities to check out this issue?
>
> What I did to observe the write-patterns of various file-systems was
> to create a ram-disk using BUSE: https://github.com/acozzette/BUSE
> It delivers an example-program which can be modified to log each
> write-access, which I imported as CSV into LibreOffice for
> visualization.
can you explain better?
Regards,
--
,,,
(o o)
======oOO==(_)==OOo======
Gianluca Renzi
R&D
phone: +39.0542.609120
fax: +39.0542.609212
.oooO Oooo.
======( )==( )=======
\ ( ) /
\_) (_/
===================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(".)_/¯
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-02-12 14:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 10:16 Hello list! gianluca
[not found] ` <52FB49EA.30004-RMR/+jklkADqD7ZJT3/+rDUZDU+1vuVT@public.gmane.org>
2014-02-12 13:04 ` Clemens Eisserer
[not found] ` <CAFvQSYTuM7Zjfz47UGU3KnTgH1iSRWiiZ3iSqXUiu7MKFnOmFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-12 14:16 ` gianluca [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=52FB822C.1060208@eurekelettronica.it \
--to=gianlucarenzi-rmr/+jklkadqd7zjt3/+rduzdu+1vuvt@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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