From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: jack@suse.cz, xfs@oss.sgi.com
Subject: Re: [PATCH 0/6 V2] xfs: upfront block zeroing for DAX
Date: Sat, 7 Nov 2015 09:32:38 +1100 [thread overview]
Message-ID: <20151106223238.GT10656@dastard> (raw)
In-Reply-To: <20151105234827.GA5771@linux.intel.com>
On Thu, Nov 05, 2015 at 04:48:27PM -0700, Ross Zwisler wrote:
> On Mon, Oct 19, 2015 at 02:27:12PM +1100, Dave Chinner wrote:
> > Hi folks,
> >
> > This is an updated patch set that was first posted here:
> >
> > http://oss.sgi.com/archives/xfs/2015-10/msg00006.html
> >
> > I've dropped the DAX locking revert patch from it; that's on it's
> > way to Linus via other channels and is essentially independent to
> > this set of XFS changes.
> >
> > The only real change in the XFS code between the two versions is the
> > addition of XFS_TRANS_RESERVE in the DAX path in
> > xfs_iomap_write_direct() to allow it to dip into the reserve block
> > pool for unwritten extent conversion rather than reporting ENOSPC.
> >
> > Patches are against 4.3-rc5 + XFS for-next branch.
> >
> > -Dave.
>
> Hey Dave,
>
> I was going to start testing these, but I'm having trouble finding a baseline
> where they apply cleanly. It looks like xfs/for-next already contains v1 of
> the series, and they don't seem to apply cleanly to the current
> xfs/xfs-misc-fixes-for-4.4-2 nor to v4.3. The xfs repo I'm looking at is
> git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
The xfs-dax-updates branch of that kernel contains the v3 version of
the patches I posted a few days ago. i.e. just pull the for-next
branch of the XFS tree, because that already contains all the
patches integrated into the rest of the XFS for-next tree...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-11-06 22:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 3:27 [PATCH 0/6 V2] xfs: upfront block zeroing for DAX Dave Chinner
2015-10-19 3:27 ` [PATCH 1/6] xfs: fix inode size update overflow in xfs_map_direct() Dave Chinner
2015-10-29 14:27 ` Brian Foster
2015-10-19 3:27 ` [PATCH 2/6] xfs: introduce BMAPI_ZERO for allocating zeroed extents Dave Chinner
2015-10-29 14:27 ` Brian Foster
2015-10-29 23:35 ` Dave Chinner
2015-10-30 12:36 ` Brian Foster
2015-11-02 1:21 ` Dave Chinner
2015-10-19 3:27 ` [PATCH 3/6] xfs: Don't use unwritten extents for DAX Dave Chinner
2015-10-29 14:29 ` Brian Foster
2015-10-29 23:37 ` Dave Chinner
2015-10-30 12:36 ` Brian Foster
2015-11-02 1:14 ` Dave Chinner
2015-11-02 14:15 ` Brian Foster
2015-11-02 21:44 ` Dave Chinner
2015-11-02 21:44 ` Dave Chinner
2015-11-02 21:44 ` Dave Chinner
2015-11-03 3:53 ` Dan Williams
2015-11-03 3:53 ` Dan Williams
2015-11-03 3:53 ` Dan Williams
2015-11-03 5:04 ` Dave Chinner
2015-11-03 5:04 ` Dave Chinner
2015-11-04 0:50 ` Ross Zwisler
2015-11-04 0:50 ` Ross Zwisler
2015-11-04 1:02 ` Dan Williams
2015-11-04 1:02 ` Dan Williams
2015-11-04 4:46 ` Ross Zwisler
2015-11-04 4:46 ` Ross Zwisler
2015-11-04 9:06 ` Jan Kara
2015-11-04 9:06 ` Jan Kara
2015-11-04 15:35 ` Ross Zwisler
2015-11-04 15:35 ` Ross Zwisler
2015-11-04 17:21 ` Jan Kara
2015-11-04 17:21 ` Jan Kara
2015-11-03 9:16 ` Jan Kara
2015-11-03 9:16 ` Jan Kara
2015-10-19 3:27 ` [PATCH 4/6] xfs: DAX does not use IO completion callbacks Dave Chinner
2015-10-29 14:29 ` Brian Foster
2015-10-29 23:39 ` Dave Chinner
2015-10-30 12:37 ` Brian Foster
2015-10-19 3:27 ` [PATCH 5/6] xfs: add ->pfn_mkwrite support for DAX Dave Chinner
2015-10-29 14:30 ` Brian Foster
2015-10-19 3:27 ` [PATCH 6/6] xfs: xfs_filemap_pmd_fault treats read faults as write faults Dave Chinner
2015-10-29 14:30 ` Brian Foster
2015-11-05 23:48 ` [PATCH 0/6 V2] xfs: upfront block zeroing for DAX Ross Zwisler
2015-11-06 22:32 ` Dave Chinner [this message]
2015-11-06 18:12 ` Boylston, Brian
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=20151106223238.GT10656@dastard \
--to=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=ross.zwisler@linux.intel.com \
--cc=xfs@oss.sgi.com \
/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.