From: Lukáš Czerner <lczerner@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v3 08/18] gfs2: use ->invalidatepage() length argument
Date: Tue, 9 Apr 2013 15:27:04 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1304091516210.22989@localhost> (raw)
In-Reply-To: <686810645.4576872.1365512960001.JavaMail.root@redhat.com>
On Tue, 9 Apr 2013, Bob Peterson wrote:
> Date: Tue, 9 Apr 2013 09:09:20 -0400 (EDT)
> From: Bob Peterson <rpeterso@redhat.com>
> To: Lukas Czerner <lczerner@redhat.com>
> Cc: linux-mm at kvack.org, linux-kernel at vger.kernel.org,
> linux-fsdevel at vger.kernel.org, linux-ext4 at vger.kernel.org,
> cluster-devel at redhat.com
> Subject: Re: [PATCH v3 08/18] gfs2: use ->invalidatepage() length argument
>
> Hi,
>
> ----- Original Message -----
> | ->invalidatepage() aop now accepts range to invalidate so we can make
> | use of it in gfs2_invalidatepage().
> |
> | Signed-off-by: Lukas Czerner <lczerner@redhat.com>
> | Cc: cluster-devel at redhat.com
> | ---
> | fs/gfs2/aops.c | 9 +++++++--
> | 1 files changed, 7 insertions(+), 2 deletions(-)
> |
> | diff --git a/fs/gfs2/aops.c b/fs/gfs2/aops.c
> | index 37093ba..ea920bf 100644
> | --- a/fs/gfs2/aops.c
> | +++ b/fs/gfs2/aops.c
> | @@ -947,24 +947,29 @@ static void gfs2_invalidatepage(struct page *page,
> | unsigned int offset,
> | unsigned int length)
> | {
> | struct gfs2_sbd *sdp = GFS2_SB(page->mapping->host);
> | + unsigned int stop = offset + length;
> | + int partial_page = (offset || length < PAGE_CACHE_SIZE);
> | struct buffer_head *bh, *head;
> | unsigned long pos = 0;
> |
> | BUG_ON(!PageLocked(page));
> | - if (offset == 0)
> | + if (!partial_page)
> | ClearPageChecked(page);
> | if (!page_has_buffers(page))
> | goto out;
> |
> | bh = head = page_buffers(page);
> | do {
> | + if (pos + bh->b_size > stop)
> | + return;
> | +
>
> I always regret it when I review something this early in the morning,
> or post before the caffeine has taken full effect. But...
> Shouldn't the statement above be (1) ">= stop" and (2) goto out;?
Hi,
1: No, because "stop = offset + length" and we're comparing it with
"pos + bh->b_size". If it would be ">=" then we would always miss
the last buffer. Let's assume pos = 0, b_size = 1024 and we're
invalidating offset = 0 and length = 1024 .. the rest you can try
for yourself :)
2: No, because if this condition is true, we can never have full page
invalidate. With full page invalidation we'll walk all the
buffers within the page hence we would jump our of the cycle when
"bh == head".
Thanks!
-Lukas
>
> | if (offset <= pos)
> | gfs2_discard(sdp, bh);
> | pos += bh->b_size;
> | bh = bh->b_this_page;
> | } while (bh != head);
> | out:
> | - if (offset == 0)
> | + if (!partial_page)
> | try_to_release_page(page, 0);
> | }
>
> Regards,
>
> Bob Peterson
> Red Hat File Systems
>
next prev parent reply other threads:[~2013-04-09 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1365498867-27782-1-git-send-email-lczerner@redhat.com>
2013-04-09 9:14 ` [Cluster-devel] [PATCH v3 08/18] gfs2: use ->invalidatepage() length argument Lukas Czerner
2013-04-09 9:29 ` Steven Whitehouse
2013-04-09 13:09 ` Bob Peterson
2013-04-09 13:27 ` Lukáš Czerner [this message]
2013-04-23 14:16 ` Theodore Ts'o
2013-04-23 14:17 ` Theodore Ts'o
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=alpine.LFD.2.00.1304091516210.22989@localhost \
--to=lczerner@redhat.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;
as well as URLs for NNTP newsgroup(s).