From: Fan Li <fanofcode.li@samsung.com>
To: 'Chao Yu' <chao@kernel.org>, 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/3] f2fs: support finding extents after isize
Date: Thu, 31 Dec 2015 11:37:01 +0800 [thread overview]
Message-ID: <001901d1437c$9b4b15d0$d1e14170$@samsung.com> (raw)
In-Reply-To: <5683DBD5.1050509@kernel.org>
> -----Original Message-----
> From: Chao Yu [mailto:chao@kernel.org]
> Sent: Wednesday, December 30, 2015 9:28 PM
> To: Fan Li; 'Jaegeuk Kim'
> Cc: linux-f2fs-devel@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH 2/3] f2fs: support finding extents after isize
>
> Hi,
>
> On 12/30/15 5:17 PM, Fan Li wrote:
> > f2fs allows preallocation beyond isize, but f2fs_fiemap only look up
> > extents within isize. Therefore add this support.
> >
> > Note: It's possible that there are holes after isize, for example,
> > fallocate multiple discontinuous extents after isize with
> > FALLOC_FL_KEEP_SIZE set. Since I can tell no differences between EOF
> > and holes from return of get_data_block, I'm afaid this patch can't
> > support such scenarios.
>
> As you mentioned, preallocated block beyond isize can be allocated in f2fs, and we are trying to support mapping extents across
> whole data space of inode, so why we treat theses extents inside i_size and outside i_size separately? IMO, instead using i_size,
we
> should use max blocks as boundary.
>
> Most important, this interface still can't support finding all extents after i_size, which looks buggy for our user.
Notice that this issue exists before my patch, by adding this patch, at least now it can support more scenarios
such as fallocate a range right after isize. I'd say it's an improvement.
use max blocks as boundary would get us the precise result, but it also means after we reach the EOF, we still
need to look up every block between the EOF and sb-> s_maxbytes to make sure the EOF is true, that's
about 4TB or 10^9 blocks.
And it affects all scenarios where the search range covers the last extent in the file, not just extents beyond
isize. I think this price is too high to pay.
I was hoping that I can make f2fs_map_block return an EOF to solve this problem some time later, or anyone
have a better idea?
>
> Thanks,
>
> >
> >
> > Signed-off-by: Fan li <fanofcode.li@samsung.com>
> > ---
> > fs/f2fs/data.c | 7 +------
> > 1 file changed, 1 insertion(+), 6 deletions(-)
> >
> > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index a9a4d89..f89cf07
> > 100644
> > --- a/fs/f2fs/data.c
> > +++ b/fs/f2fs/data.c
> > @@ -798,12 +798,6 @@ int f2fs_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
> > isize = i_size_read(inode);
> >
> > mutex_lock(&inode->i_mutex);
> > - if (start >= isize)
> > - goto out;
> > -
> > - if (start + len > isize)
> > - len = isize - start;
> > -
> > if (logical_to_blk(inode, len) == 0)
> > len = blk_to_logical(inode, 1);
> >
> > @@ -829,6 +823,7 @@ next:
> > * punch holes beyond isize and keep size unchanged.
> > */
> > flags |= FIEMAP_EXTENT_LAST;
> > + last_blk = start_blk - 1;
> > }
> >
> > if (size)
> >
------------------------------------------------------------------------------
next prev parent reply other threads:[~2015-12-31 3:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 9:17 [PATCH 2/3] f2fs: support finding extents after isize Fan Li
2015-12-30 13:27 ` Chao Yu
2015-12-31 3:37 ` Fan Li [this message]
2015-12-31 6:34 ` Chao Yu
2016-01-04 5:57 ` Fan Li
2016-01-04 6:55 ` Jaegeuk Kim
2016-01-04 11:13 ` Fan Li
2016-01-04 23:14 ` Jaegeuk Kim
2016-01-05 2:37 ` Fan Li
2016-01-05 3:08 ` Jaegeuk Kim
2016-01-05 7:22 ` Fan Li
2016-01-05 18:11 ` Jaegeuk Kim
2016-01-05 3:19 ` Chao Yu
2016-01-05 3:29 ` Jaegeuk Kim
2016-01-05 9:36 ` Chao Yu
2016-01-04 10:00 ` Chao Yu
2016-01-04 10:55 ` Fan Li
2016-01-05 3:48 ` Chao Yu
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='001901d1437c$9b4b15d0$d1e14170$@samsung.com' \
--to=fanofcode.li@samsung.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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