From: Coly Li <colyli@suse.de>
To: linux-bcache@vger.kernel.org
Cc: linux-block@vger.kernel.org, Coly Li <colyli@suse.de>
Subject: [RFC PATCH 0/4] bcache-tools: changes for large bucket size
Date: Mon, 6 Jul 2020 00:04:36 +0800 [thread overview]
Message-ID: <20200705160440.5801-1-colyli@suse.de> (raw)
These are user space tools changes necessary for bcache large bucket
size. When setting bucket size with '-u' larger than 16MB for cache
device, BCACHE_SB_VERSION_CDEV_WITH_FEATURES will be set automatically.
Otherwise, the new added members in super block won't be touched.
Coly Li
---
Coly Li (4):
bcache-tools: comments offset for members of struct cache_sb
struct_offset: print offset of each member of the on-disk data
structure
bcache-tools: The new super block version
BCACHE_SB_VERSION_BDEV_WITH_FEATURES
bcache-tools: add large_bucket incompat feature
Makefile | 6 +-
bcache.h | 153 ++++++++++++++++++++++++++++++++++++++----------
features.c | 24 ++++++++
lib.c | 24 ++++++++
lib.h | 2 +
make.c | 36 ++++++++----
struct_offset.c | 63 ++++++++++++++++++++
7 files changed, 265 insertions(+), 43 deletions(-)
create mode 100644 features.c
create mode 100644 struct_offset.c
--
2.26.2
next reply other threads:[~2020-07-05 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 16:04 Coly Li [this message]
2020-07-05 16:04 ` [RFC PATCH 1/4] bcache-tools: comments offset for members of struct cache_sb Coly Li
2020-07-05 16:04 ` [RFC PATCH 2/4] struct_offset: print offset of each member of the on-disk data structure Coly Li
2020-07-05 16:04 ` [RFC PATCH 3/4] bcache-tools: The new super block version BCACHE_SB_VERSION_BDEV_WITH_FEATURES Coly Li
2020-07-05 16:04 ` [RFC PATCH 4/4] bcache-tools: add large_bucket incompat feature Coly Li
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=20200705160440.5801-1-colyli@suse.de \
--to=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@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).