From: Jie Liu <jeff.liu@oracle.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v4] xfs: probe data buffer from page cache for unwritten extents
Date: Sat, 21 Jul 2012 14:24:36 +0800 [thread overview]
Message-ID: <500A4B24.40908@oracle.com> (raw)
In-Reply-To: <5009A786.3080500@sgi.com>
On 07/21/2012 02:46 AM, Mark Tinguely wrote:
> On 07/20/12 03:28, Jeff Liu wrote:
>> Hi All,
>>
>> According to Mark and Christoph's comments for v3, except optimizing
>> xfs_seek_data() with unwritten extents
>> probing, the xfs_seek_hole() is also refined to that in this version.
>>
>>
>
> Just some feedback.
>
> Test program fragment:
>
> ret = do_fallocate(fd, 512*1024, 256*1024, 0);
> if (ret < 0)
> goto out;
> pwrite(fd, buf, 4096, 1024*516);
> lseek(fd, 800*1024, SEEK_SET);
> ret = write(fd, buf, bufsz);
> if (ret < 0)
> goto out;
>
> Output:
>
> HOLE/DATA at 512K 786432 / 528384 <- undiscovered hole here
> HOLE/DATA at 516K 786432 / 528384 <- okay, data but we should
> return next page as hole.
> HOLE/DATA at 520K 532480 / 819200 <- hole is discovered because
> there is no trailing data
Oops! for xfs_seek_hole(), I should use min_t() to pre-claculate offset
before searching page cache.
Thanks for your prompt feedback. I'll do some extra tests and post the
revised soon.
Thanks,
-Jeff
>
> --Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-21 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 8:28 [PATCH v4] xfs: probe data buffer from page cache for unwritten extents Jeff Liu
2012-07-20 18:46 ` Mark Tinguely
2012-07-21 6:24 ` Jie Liu [this message]
2012-07-22 4:57 ` Christoph Hellwig
2012-07-22 5:29 ` Jie Liu
2012-07-22 6:28 ` Christoph Hellwig
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=500A4B24.40908@oracle.com \
--to=jeff.liu@oracle.com \
--cc=tinguely@sgi.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.