The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: David Timber <dxdt@dev.snart.me>
Cc: Christoph Hellwig <hch@infradead.org>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] fat: add noflush mount option
Date: Tue, 25 Aug 2026 21:40:19 -0700	[thread overview]
Message-ID: <ao5uM1BFiwROcKsb@infradead.org> (raw)
In-Reply-To: <aa36b1de-70d9-4234-a240-770fe66aa19b@dev.snart.me>

On Wed, Aug 26, 2026 at 01:13:29PM +0900, David Timber wrote:
> It probably had something to do with DOS and/or Windows implementation,
> maybe a "monkey see, monkey do" situation. I think this is why FAT on
> Windows is quite slow to this day(again, I might be wrong so don't quote
> me on this).
> 
> Whoever first came up with the idea was probably worried too much about
> users(who are not familiar with UNIX systems) unplugging removable
> devices without giving the OS an opportunity to sync. I have to say
> that, compared to Windows' default behaviour, the default 5 seconds of
> vm.dirty_writeback is quite aggressive and that's why we have the flush
> option in the first place...
> 
> But I still think being able to flip the option on the fly should come
> in really handy in embedded systems that just can't afford to do
> explicit sync.

As I said, no objection to adding the option, but I think addressing
the root cause in addition would be very helpfu.


      reply	other threads:[~2026-08-26  4:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 17:37 [RFC PATCH] fat: add noflush mount option David Timber
2026-08-24  9:45 ` OGAWA Hirofumi
2026-08-25  1:10   ` David Timber
2026-08-25  4:31     ` OGAWA Hirofumi
2026-08-26  4:22       ` David Timber
2026-08-26  7:21         ` OGAWA Hirofumi
2026-08-26  8:00           ` David Timber
2026-08-26  8:57             ` OGAWA Hirofumi
2026-08-25  5:51 ` Christoph Hellwig
2026-08-26  4:13   ` David Timber
2026-08-26  4:40     ` Christoph Hellwig [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=ao5uM1BFiwROcKsb@infradead.org \
    --to=hch@infradead.org \
    --cc=dxdt@dev.snart.me \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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