linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH v3 3/6] btrfs: Make compress_file_range take only struct async_chunk
Date: Thu, 21 Feb 2019 13:57:14 +0200	[thread overview]
Message-ID: <20190221115717.5128-4-nborisov@suse.com> (raw)
In-Reply-To: <20190221115717.5128-1-nborisov@suse.com>

All context this function needs is held within struct async_chunk.
Currently we not only pass the struct but also every individual member.
This is redundant, simplify it by only passing struct async_chunk and
leaving it to compress_file_range to extract the values it requires.
No functional changes.

Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
 fs/btrfs/inode.c | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index d61dd538d2b4..d566e15f8c58 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -449,14 +449,14 @@ static inline void inode_should_defrag(struct btrfs_inode *inode,
  * are written in the same order that the flusher thread sent them
  * down.
  */
-static noinline void compress_file_range(struct inode *inode,
-					struct page *locked_page,
-					u64 start, u64 end,
-					struct async_chunk *async_cow,
-					int *num_added)
+static noinline void compress_file_range(struct async_chunk *async_cow,
+					 int *num_added)
 {
+	struct inode *inode = async_cow->inode;
 	struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
 	u64 blocksize = fs_info->sectorsize;
+	u64 start = async_cow->start;
+	u64 end = async_cow->end;
 	u64 actual_end;
 	int ret = 0;
 	struct page **pages = NULL;
@@ -675,9 +675,9 @@ static noinline void compress_file_range(struct inode *inode,
 	 * to our extent and set things up for the async work queue to run
 	 * cow_file_range to do the normal delalloc dance.
 	 */
-	if (page_offset(locked_page) >= start &&
-	    page_offset(locked_page) <= end)
-		__set_page_dirty_nobuffers(locked_page);
+	if (page_offset(async_cow->locked_page) >= start &&
+	    page_offset(async_cow->locked_page) <= end)
+		__set_page_dirty_nobuffers(async_cow->locked_page);
 		/* unlocked later on in the async handlers */
 
 	if (redirty)
@@ -1141,9 +1141,7 @@ static noinline void async_cow_start(struct btrfs_work *work)
 	int num_added = 0;
 	async_cow = container_of(work, struct async_chunk, work);
 
-	compress_file_range(async_cow->inode, async_cow->locked_page,
-			    async_cow->start, async_cow->end, async_cow,
-			    &num_added);
+	compress_file_range(async_cow, &num_added);
 	if (num_added == 0) {
 		btrfs_add_delayed_iput(async_cow->inode);
 		async_cow->inode = NULL;
-- 
2.17.1


  parent reply	other threads:[~2019-02-21 11:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 11:57 [PATCH v3 0/6] Compress path cleanups Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 1/6] btrfs: Refactor cow_file_range_async Nikolay Borisov
2019-02-21 13:15   ` Johannes Thumshirn
2019-02-21 13:25     ` Nikolay Borisov
2019-02-21 15:07       ` Johannes Thumshirn
2019-02-21 15:09         ` Nikolay Borisov
2019-02-22 18:05           ` David Sterba
2019-02-22 18:13   ` David Sterba
2019-02-21 11:57 ` [PATCH v3 2/6] btrfs: Remove fs_info from struct async_chunk Nikolay Borisov
2019-02-21 13:07   ` Johannes Thumshirn
2019-02-21 11:57 ` Nikolay Borisov [this message]
2019-02-21 13:07   ` [PATCH v3 3/6] btrfs: Make compress_file_range take only " Johannes Thumshirn
2019-02-21 11:57 ` [PATCH v3 4/6] btrfs: Replace clear_extent_bit with unlock_extent Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 5/6] btrfs: Set iotree only once in submit_compressed_extents Nikolay Borisov
2019-02-21 11:57 ` [PATCH v3 6/6] btrfs: Factor out common extent locking code " Nikolay Borisov

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=20190221115717.5128-4-nborisov@suse.com \
    --to=nborisov@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).