From: Mark Tinguely <tinguely@sgi.com>
To: jeff.liu@oracle.com
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v5 2/4]xfs: Introduce a new function to find the desired type of offset from page cache
Date: Mon, 30 Jul 2012 15:00:16 -0500 [thread overview]
Message-ID: <5016E7D0.8060903@sgi.com> (raw)
In-Reply-To: <5011631F.40005@oracle.com>
On 07/26/12 10:32, Jeff Liu wrote:
> This function is called by xfs_seek_data() and xfs_seek_hole() to find
> the desired offset from page cache.
>
> Signed-off-by: Jie Liu<jeff.liu@oracle.com>
Hopefully, I am not being a pain....
I just noticed that if trylock() failed you return found==0.
Wouldn't it be safer/more correct to assume a page that failed a
try_lock to be data?
> + if (nr_pages == 0) {
> + if (type == HOLE_OFF) {
> + if (coff == *offset)
> + found = true;
is this necessary? wouldn't the next test also cover the above condition?
> + if (coff< endoff) {
> + found = true;
> + *offset = coff;
> + }
> + }
I like informative comments, but some are bit verbose. I will pick on
this one:
+ /*
+ * Page index is out of range, we need to deal with
+ * hole search condition in paticular if that is the
+ * desired type for the lookup.
+ * stepping into the block buffer checkup, it probably
+ * means that there is no page mapped at all in the
+ * specified range to search, so we found a hole.
+ * If we have already done some block buffer checking
+ * and found one or more data buffers before, in this
+ * case, the coff is already updated and it point to
+ * the end of the last data buffer, so the left range
+ * behind it might be a hole. In either case, we will
+ * return the coff to indicate a hole's location because
+ * it must be greater than or equal to the search start.
+ */
just a crude simplification - maybe it is too terse:
/*
* coff is the current offset of the page being tested.
* If the next page index is beyond the extent of interest,
* then we are done searching with the data search is
* false and hole search is true at the last coff.
*/
For holes you are looking for (page->index != coff) for every page, but
in a indirect way. It had me a little confused, but eventually I figured
it out. I am not sure if a doing that comparison directly would overly
complicate the data search path.
Good work.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-30 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 8:56 [PATCH v5 2/4]xfs: Introduce a new function to find the desired type of offset from page cache Jeff Liu
2012-07-26 15:16 ` Jeff Liu
2012-07-26 15:32 ` Jeff Liu
2012-07-30 20:00 ` Mark Tinguely [this message]
2012-07-31 6:04 ` Jeff Liu
2012-07-30 23:43 ` Dave Chinner
2012-07-31 7:26 ` Jie Liu
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=5016E7D0.8060903@sgi.com \
--to=tinguely@sgi.com \
--cc=jeff.liu@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox