From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: akpm@linux-foundation.org, "Michal Hocko" <mhocko@suse.com>,
jack@suse.cz, "Peter Zijlstra" <peterz@infradead.org>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Dave Chinner" <david@fromorbit.com>,
"Andreas Dilger" <adilger.kernel@dilger.ca>,
hch@lst.de, "Matthew Wilcox" <mawilcox@microsoft.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Jeff Moyer" <jmoyer@redhat.com>,
"Ingo Molnar" <mingo@redhat.com>,
ross.zwisler@linux.intel.com, linux-ext4@vger.kernel.org,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
linux-fsdevel@vger.kernel.org,
"Jérôme Glisse" <jglisse@redhat.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Gerald Schaefer" <gerald.schaefer@de.ibm.com>,
linux-nvdimm@lists.01.org, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [PATCH v4 00/18] dax: fix dma vs truncate/hole-punch
Date: Thu, 4 Jan 2018 09:17:55 +0100 [thread overview]
Message-ID: <20180104081755.GD2548@lst.de> (raw)
In-Reply-To: <151407695916.38751.2866053440557472361.stgit@dwillia2-desk3.amr.corp.intel.com>
> So far this solution only targets xfs since it already implements
> xfs_break_layouts in all the locations that would need this
> synchronization. It applies on top of the vmem_altmap / dev_pagemap
> reworks from Christoph.
Those got a rebase since your posting of this series, btw.
prev parent reply other threads:[~2018-01-04 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 0:56 [PATCH v4 00/18] dax: fix dma vs truncate/hole-punch Dan Williams
[not found] ` <151407695916.38751.2866053440557472361.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-12-24 0:57 ` [PATCH v4 13/18] ext4: use DEFINE_FSDAX_AOPS Dan Williams
[not found] ` <151407703002.38751.15305085717541373826.stgit-p8uTFz9XbKj2zm6wflaqv1nYeNYlB/vhral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-01-04 8:29 ` Christoph Hellwig
2018-01-04 8:17 ` 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=20180104081755.GD2548@lst.de \
--to=hch@lst.de \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@fromorbit.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jack@suse.cz \
--cc=jglisse@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mawilcox@microsoft.com \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).