linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: JH <jupiter.hce@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: File IO write flush time span
Date: Tue, 25 Feb 2020 19:45:32 +1100	[thread overview]
Message-ID: <CAA=hcWS1WPA-Sb93rGgXYFnJckYtwypTXS2LTZ=HhLRiUfYnyw@mail.gmail.com> (raw)
In-Reply-To: <CAFLxGvwUMsXCO2yG27z7av3eAajwEzuHafX9Fimejc_u2mpGig@mail.gmail.com>

Hi Richard,

On 2/25/20, Richard Weinberger <richard.weinberger@gmail.com> wrote:
> On Tue, Feb 25, 2020 at 6:58 AM JH <jupiter.hce@gmail.com> wrote:
>>
>> Hi,
>>
>> If I write a file to a UBIFS volume, how long the mtd will write it
>> from cache to physical NAND? I try to understand in what time span
>> those IO writing in cache will be lost if the power is turned off
>> (lost power).
>
> What cache do you have in mind?
> As soon ubiupdatevol terminates, the volume is in stable state.

I was actually talking about applications write files to a UBIFS
volume mounted as RW in Linux, let's say if I write a file by vi, will
it immediately flush to the NAND or will it stay in cache until some
algorithm in MTD to erase NAND pages and flush the cache to NAND page
based on size of output or time, is it correct?

Thank you.

Kind regards,

- jh

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2020-02-25  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  5:58 File IO write flush time span JH
2020-02-25  8:31 ` Richard Weinberger
2020-02-25  8:45   ` JH [this message]
2020-02-25  8:54     ` Richard Weinberger

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=hcWS1WPA-Sb93rGgXYFnJckYtwypTXS2LTZ=HhLRiUfYnyw@mail.gmail.com' \
    --to=jupiter.hce@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@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;
as well as URLs for NNTP newsgroup(s).