RE: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-04 Thread Namjae Jeon
> > > > > > > > That said, I wonder whether we even care about a merge in the right > > > shift case since we haven't punched a hole in the file and thus have not > > > changed the "neighbors" of any of the extents we're shuffling around. I > > > would think any extents that are already contiguous

Re: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-04 Thread Brian Foster
On Thu, Dec 04, 2014 at 08:19:50PM +0900, Namjae Jeon wrote: > > > > Hi Namjae, > Hi Brian, > > > > > Here are some review notes. I haven't got to any of the test code or > > played around with it just yet... > Thanks for your reivew :) > No problem. :) > > > > > > diff --git

RE: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-04 Thread Namjae Jeon
> > Hi Namjae, Hi Brian, > > Here are some review notes. I haven't got to any of the test code or > played around with it just yet... Thanks for your reivew :) > > > > diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c > > index 79c9819..da01890 100644 > > ---

RE: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-04 Thread Namjae Jeon
Hi Namjae, Hi Brian, Here are some review notes. I haven't got to any of the test code or played around with it just yet... Thanks for your reivew :) diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c index 79c9819..da01890 100644 --- a/fs/xfs/libxfs/xfs_bmap.c +++

Re: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-04 Thread Brian Foster
On Thu, Dec 04, 2014 at 08:19:50PM +0900, Namjae Jeon wrote: Hi Namjae, Hi Brian, Here are some review notes. I haven't got to any of the test code or played around with it just yet... Thanks for your reivew :) No problem. :) diff --git a/fs/xfs/libxfs/xfs_bmap.c

RE: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-04 Thread Namjae Jeon
That said, I wonder whether we even care about a merge in the right shift case since we haven't punched a hole in the file and thus have not changed the neighbors of any of the extents we're shuffling around. I would think any extents that are already contiguous as such are

Re: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-02 Thread Brian Foster
On Mon, Nov 24, 2014 at 03:16:33PM +0900, Namjae Jeon wrote: > This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS. > > 1) Make sure that both offset and len are block size aligned. > 2) Update the i_size of inode by len bytes. > 3) Compute the file's logical block number against

Re: [PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-12-02 Thread Brian Foster
On Mon, Nov 24, 2014 at 03:16:33PM +0900, Namjae Jeon wrote: This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS. 1) Make sure that both offset and len are block size aligned. 2) Update the i_size of inode by len bytes. 3) Compute the file's logical block number against offset.

[PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-11-23 Thread Namjae Jeon
This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS. 1) Make sure that both offset and len are block size aligned. 2) Update the i_size of inode by len bytes. 3) Compute the file's logical block number against offset. If the computed block number is not the starting block of the

[PATCH v6 2/10] xfs: Add support FALLOC_FL_INSERT_RANGE for fallocate

2014-11-23 Thread Namjae Jeon
This patch implements fallocate's FALLOC_FL_INSERT_RANGE for XFS. 1) Make sure that both offset and len are block size aligned. 2) Update the i_size of inode by len bytes. 3) Compute the file's logical block number against offset. If the computed block number is not the starting block of the