From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 1/3] btrfs: Introduce struct btrfs_io_geometry
Date: Mon, 3 Jun 2019 12:05:03 +0300 [thread overview]
Message-ID: <20190603090505.16800-2-nborisov@suse.com> (raw)
In-Reply-To: <20190603090505.16800-1-nborisov@suse.com>
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
---
fs/btrfs/volumes.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/fs/btrfs/volumes.h b/fs/btrfs/volumes.h
index a7121d72388f..7c1ddf35b7d4 100644
--- a/fs/btrfs/volumes.h
+++ b/fs/btrfs/volumes.h
@@ -23,6 +23,15 @@ struct btrfs_pending_bios {
struct bio *tail;
};
+struct btrfs_io_geometry {
+ u64 len; /* remaining bytes in chunk */
+ u64 offset; /* offset of logical address in chunk */
+ u64 stripe_len; /* len of single io stripe */
+ u64 stripe_nr; /* number of stripe where address falls */
+ u64 stripe_offset; /* offset of stripe in chunk */
+ u64 raid56_stripe_offset; /* offset of raid56 stripe into the chunk */
+};
+
/*
* Use sequence counter to get consistent device stat data on
* 32-bit processors.
--
2.17.1
next prev parent reply other threads:[~2019-06-03 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 9:05 [PATCH 0/3] refactoring __btrfs_map_block Nikolay Borisov
2019-06-03 9:05 ` Nikolay Borisov [this message]
2019-06-05 7:35 ` [PATCH 1/3] btrfs: Introduce struct btrfs_io_geometry Johannes Thumshirn
2019-06-05 12:37 ` David Sterba
2019-06-03 9:05 ` [PATCH 2/3] btrfs: Introduce btrfs_io_geometry Nikolay Borisov
2019-06-05 8:01 ` Johannes Thumshirn
2019-06-12 16:31 ` David Sterba
2019-06-03 9:05 ` [PATCH 3/3] btrfs: Use btrfs_io_geometry appropriately Nikolay Borisov
2019-06-12 16:29 ` 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=20190603090505.16800-2-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