From: David Woodhouse <dwmw2@infradead.org>
To: Estelle HAMMACHE <estelle.hammache@st.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 and frequent/small write operations
Date: Tue, 05 Apr 2005 10:27:30 +0100 [thread overview]
Message-ID: <1112693250.4397.27.camel@localhost.localdomain> (raw)
In-Reply-To: <42524FBD.C418A0E6@st.com>
On Tue, 2005-04-05 at 10:43 +0200, Estelle HAMMACHE wrote:
> Sorry for the confusion... I'm glad this erroneous notion
> is corrected.
Actually -- looking briefly at generic_osync_inode(), I'm not entirely
convinced that we _do_ correctly flush after an O_SYNC write. Do we need
to set I_DIRTY_DATASYNC when we have outstanding data in the wbuf, and
implement write_inode() to make it get flushed?
--
dwmw2
prev parent reply other threads:[~2005-04-05 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 13:58 JFFS2 and frequent/small write operations Gianluca Moro
2005-04-04 17:15 ` Sergei Sharonov
2005-04-04 18:55 ` David Woodhouse
2005-04-04 21:08 ` Sergei Sharonov
2005-04-05 8:43 ` Estelle HAMMACHE
2005-04-05 9:27 ` David Woodhouse [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=1112693250.4397.27.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=estelle.hammache@st.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.