linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Collins <allison.henderson@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [Lsf-pc] [LSF/MM/BPF TOPIC] Atomic Writes
Date: Thu, 13 Feb 2020 15:33:08 -0700	[thread overview]
Message-ID: <e88c2f96-fdbb-efb5-d7e2-94bfefbe8bfa@oracle.com> (raw)

Hi all,

I know there's a lot of discussion on the list right now, but I'd like 
to get this out before too much time gets away.  I would like to propose 
the topic of atomic writes.  I realize the topic has been discussed 
before, but I have not found much activity for it recently so perhaps we 
can revisit it.  We do have a customer who may have an interest, so I 
would like to discuss the current state of things, and how we can move 
forward.  If efforts are in progress, and if not, what have we learned 
from the attempt.

I also understand there are multiple ways to solve this problem that 
people may have opinions on.  I've noticed some older patch sets trying 
to use a flag to control when dirty pages are flushed, though I think 
our customer would like to see a hardware solution via NVMe devices.  So 
I would like to see if others have similar interests as well and what 
their thoughts may be.  Thanks everyone!

Allison

             reply	other threads:[~2020-02-13 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 22:33 Allison Collins [this message]
2020-02-14  4:42 ` [Lsf-pc] [LSF/MM/BPF TOPIC] Atomic Writes Darrick J. Wong
2020-02-15 19:53   ` Matthew Wilcox
2020-02-16 21:41     ` Dave Chinner
2020-02-20 21:30   ` Steve French

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=e88c2f96-fdbb-efb5-d7e2-94bfefbe8bfa@oracle.com \
    --to=allison.henderson@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).