public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs: compression: update the comment for alloc_compressed_bio()
Date: Tue,  5 Oct 2021 14:21:44 +0800	[thread overview]
Message-ID: <20211005062144.68489-1-wqu@suse.com> (raw)

This comment will include all parameters, not only the new
@next_stripe_start.

Signed-off-by: Qu Wenruo <wqu@suse.com>
---
 fs/btrfs/compression.c | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/fs/btrfs/compression.c b/fs/btrfs/compression.c
index 69a19d51fa35..cba82fdae7e5 100644
--- a/fs/btrfs/compression.c
+++ b/fs/btrfs/compression.c
@@ -438,9 +438,19 @@ static blk_status_t submit_compressed_bio(struct btrfs_fs_info *fs_info,
 }
 
 /*
- * To allocate a compressed_bio, which will be used to read/write on-disk data.
+ * To allocate a compressed_bio, which will be used to read/write on-disk
+ * (aka, compressed) data.
  *
- * @next_stripe_start:	Disk bytenr of next stripe start
+ * @cb:		The compressed_bio structure, which records all the needed
+ * 		info to bind the compressed data to the uncompressed page cache.
+ * @disk_byten:	The logical bytenr where the compressed data will be read from
+ * 		or written to.
+ * @endio_func:	The endio function to call after the IO for compressed data is
+ * 		finished.
+ * @next_stripe_start:
+ * 		The Return value of Logical bytenr of where next stripe start.
+ * 		To inform the caller to only fill the bio up to the stripe
+ * 		boundary.
  */
 static struct bio *alloc_compressed_bio(struct compressed_bio *cb, u64 disk_bytenr,
 					unsigned int opf, bio_end_io_t endio_func,
-- 
2.33.0


             reply	other threads:[~2021-10-05  6:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  6:21 Qu Wenruo [this message]
2021-10-05 17:18 ` [PATCH] btrfs: compression: update the comment for alloc_compressed_bio() David Sterba

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=20211005062144.68489-1-wqu@suse.com \
    --to=wqu@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