From: Howard Chu <hyc@symas.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Atomic I/Os, Transactions
Date: Sat, 09 Nov 2013 17:36:24 -0800 [thread overview]
Message-ID: <527EE318.8060907@symas.com> (raw)
Since atomic I/Os have come up recently, I thought I'd throw a wish-list item
out there for consideration. It seems to me that the notion of write barriers
was too heavy-handed. What I would like is a way to tag groups of writes. The
only ordering constraint being, writes within a group tagged N cannot be
started before all writes in group N-1 have completed. Aside from that, writes
within a group may be freely mixed and reordered with non-tagged/non-grouped
writes, and freely reordered within the group. That would allow a DB
application to commit its transactions with a consistent ordering without
requiring a full cache flush/sync/etc., thus reducing impact on overall I/O.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
reply other threads:[~2013-11-10 1:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=527EE318.8060907@symas.com \
--to=hyc@symas.com \
--cc=linux-fsdevel@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 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.