xfs
[Top] [All Lists]

Re: [PATCH 05/16] xfs: add owner field to extent allocation and freeing

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH 05/16] xfs: add owner field to extent allocation and freeing
From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Date: Mon, 28 Mar 2016 15:05:06 -0700
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160310141913.GC29058@xxxxxxxxxxxxx>
References: <1457410578-30233-1-git-send-email-david@xxxxxxxxxxxxx> <1457410578-30233-6-git-send-email-david@xxxxxxxxxxxxx> <20160310141913.GC29058@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Thu, Mar 10, 2016 at 06:19:13AM -0800, Christoph Hellwig wrote:
> On Tue, Mar 08, 2016 at 03:16:07PM +1100, Dave Chinner wrote:
> > From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
> > 
> > For the rmap btree to work, we have to fed the extent owner
> 
> s/fed/feed/

<nod>

> 
> > +/*
> > + * Ownership info for an extent.  This is used to create reverse-mapping
> > + * entries.
> > + */
> > +#define XFS_RMAP_INO_ATTR_FORK     (1)
> > +#define XFS_RMAP_BMBT_BLOCK        (2)
> 
> These are OR-able flags - it might make sense to define them as:
> 
> #define XFS_RMAP_INO_ATTR_FORK        (1 << 0)
> #define XFS_RMAP_BMBT_BLOCK   (1 << 1)
> 
> to make this more obvious.

Ok.  Will do when I merge the "separate xfs_rmap_irec flags field" patch
into the appropriate patches (like this one).

--D

> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

<Prev in Thread] Current Thread [Next in Thread>