linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Timofey Titovets <nefelim4ag@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [RFC PATCH] Btrfs: handle unaligned tail of data ranges more efficient
Date: Fri, 25 Aug 2017 09:00:36 +0300	[thread overview]
Message-ID: <85e72504-51a8-e46e-15eb-a105d1678ed1@suse.com> (raw)
In-Reply-To: <20170824211235.23152-1-nefelim4ag@gmail.com>



On 25.08.2017 00:12, Timofey Titovets wrote:
> At now while switch page bits in data ranges
> we always hande +1 page, for cover case
> where end of data range is not page aligned
> 
> Let's handle that case more obvious and efficient
> Check end aligment directly and touch +1 page
> only then needed
> 
> Signed-off-by: Timofey Titovets <nefelim4ag@gmail.com>
> ---
>  fs/btrfs/extent_io.c | 12 ++++++++++--
>  fs/btrfs/inode.c     |  6 +++++-
>  2 files changed, 15 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index 98d85d2009f8..ccb66c1485e2 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -1360,7 +1360,11 @@ void extent_range_clear_dirty_for_io(struct inode *inode, u64 start, u64 end)
>  	unsigned long end_index = end >> PAGE_SHIFT;
>  	struct page *page;
> 
> -	while (index <= end_index) {
> +	/* Don't miss unaligned end */
> +	if (end%PAGE_SIZE > 0)
> +		end_index++;

if (!IS_ALIGNED(end, PAGE_SIZE)).



> +
> +	while (index < end_index) {
>  		page = find_get_page(inode->i_mapping, index);
>  		BUG_ON(!page); /* Pages should be in the extent_io_tree */
>  		clear_page_dirty_for_io(page);
> @@ -1375,7 +1379,11 @@ void extent_range_redirty_for_io(struct inode *inode, u64 start, u64 end)
>  	unsigned long end_index = end >> PAGE_SHIFT;
>  	struct page *page;
> 
> -	while (index <= end_index) {
> +	/* Don't miss unaligned end */
> +	if (end%PAGE_SIZE > 0)
> +		end_index++;

ditto

> +
> +	while (index < end_index) {
>  		page = find_get_page(inode->i_mapping, index);
>  		BUG_ON(!page); /* Pages should be in the extent_io_tree */
>  		__set_page_dirty_nobuffers(page);
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index cb7779b08aaf..79feaea0fede 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -10745,7 +10745,11 @@ void btrfs_set_range_writeback(void *private_data, u64 start, u64 end)
>  	unsigned long end_index = end >> PAGE_SHIFT;
>  	struct page *page;
> 
> -	while (index <= end_index) {
> +	/* Don't miss unaligned end */
> +	if (end%PAGE_SIZE > 0)
> +		end_index++;
Ditto

> +
> +	while (index < end_index) {
>  		page = find_get_page(inode->i_mapping, index);
>  		ASSERT(page); /* Pages should be in the extent_io_tree */
>  		set_page_writeback(page);
> --
> 2.14.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2017-08-25  6:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 21:12 [RFC PATCH] Btrfs: handle unaligned tail of data ranges more efficient Timofey Titovets
2017-08-25  6:00 ` Nikolay Borisov [this message]

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=85e72504-51a8-e46e-15eb-a105d1678ed1@suse.com \
    --to=nborisov@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nefelim4ag@gmail.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).