From: Jamie Lokier <jamie@shareable.org>
To: Doug Graham <dgraham@nortel.com>
Cc: Josh Boyer <jwboyer@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: mtdblock caching and syncing
Date: Thu, 9 Apr 2009 19:07:24 +0100 [thread overview]
Message-ID: <20090409180724.GG14196@shareable.org> (raw)
In-Reply-To: <20090409160247.GI15952@nortel.com>
Doug Graham wrote:
> > The device in question isn't the flash. It's the mtdblock device. So
> > fsync semantics are preserved. This is the same as writing to a file
> > on a hard drive, calling fsync, and having it sit in the hard drive's
> > cache.
>
> That's a good point, and one I've wondered about before. I don't know
> much about how hard drives manage their cache, but I would assume that
> they don't leave dirty data in their cache for an unbounded period
> of time. I'd guess that data is written to the actual disk within a
> few 10s of milliseconds after being sent to the device.
Ideally, fsync() should flush data from a hard drive's cache too.
-- Jamie
next prev parent reply other threads:[~2009-04-09 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 14:15 mtdblock caching and syncing Doug Graham
2009-04-09 14:51 ` Josh Boyer
2009-04-09 16:02 ` Doug Graham
2009-04-09 17:16 ` Josh Boyer
2009-04-09 18:07 ` Jamie Lokier [this message]
2009-04-09 19:24 ` Doug Graham
2009-04-23 18:21 ` Miles Nordin
2009-04-24 15:35 ` Jamie Lokier
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=20090409180724.GG14196@shareable.org \
--to=jamie@shareable.org \
--cc=dgraham@nortel.com \
--cc=jwboyer@gmail.com \
--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.