From: JH <jupiter.hce@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: A big issue of NAND fragmentation
Date: Fri, 6 Sep 2019 21:18:16 +1000 [thread overview]
Message-ID: <CAA=hcWS4C3k0XbinsWvPLJ9KofLJTDakmGPydtDrenNv=xoizg@mail.gmail.com> (raw)
In-Reply-To: <131148461.92686.1567753326360.JavaMail.zimbra@nod.at>
On 9/6/19, Richard Weinberger <richard@nod.at> wrote:
> ----- Ursprüngliche Mail -----
>> Von: "JH" <jupiter.hce@gmail.com>
>> An: "Richard Weinberger" <richard.weinberger@gmail.com>
>> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
>> Gesendet: Freitag, 6. September 2019 08:03:55
>> Betreff: Re: A big issue of NAND fragmentation
>>
>> Yes, I use UBIFS, was your word "force" means "write" or did you
>> allude there would be an alternative to avoid forcing UBIFS persist
>> 250 bytes?
>>
>> Waiting for out of space would be too risk, alternatively, I should
>> have a UBIFS partition for the data storage, if it runs out of space,
>> it won't impact the root file system.
>>
>
> No, by force I mean forcing the filesystem to persist the data.
> For example by using fsync(),fdatasync(), O_SYNC or a sync mounted
> filesystem.
> If you don't do this, data will be cached and can be packed
> later upon write-back.
I use std::ofstream and operator<<, it does have a flush but I don't
know if the flush is a default setting or not, but obviously it is
default which caused fragmentation. More work to do, might be better
to use an old simple C write.
Thanks for the explanation.
- jupiter
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-09-06 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 1:27 A big issue of NAND fragmentation JH
2019-09-05 11:54 ` Richard Weinberger
2019-09-06 6:03 ` JH
2019-09-06 7:02 ` Richard Weinberger
2019-09-06 11:18 ` JH [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='CAA=hcWS4C3k0XbinsWvPLJ9KofLJTDakmGPydtDrenNv=xoizg@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
/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).