From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v2 0/3] gfs2: Add new resource group header fields
Date: Tue, 12 Dec 2017 13:00:18 -0500 (EST) [thread overview]
Message-ID: <1271599422.40834307.1513101618014.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20171208145942.17717-1-anprice@redhat.com>
----- Original Message -----
| These patches add new fields to struct gfs2_rgrp. The intention is to improve
| fsck performance and error checking while reducing reliance on the rindex to
| be read in order to scan through the resource groups in tools such as
| fsck.gfs2. This is part of a wider goal to obsolete gfs2's metafs, hence the
| duplication of fields from the rindex. In testing performance, these patches
| carry very little-to-no overhead.
|
| This posting will be followed by a patch set for gfs2-utils to make use of
| the new fields, and set and check them enough for testing purposes.
|
| v2: fixed cpu_to_be64/32 typos and made sure rg_skip of the last rgrp is
| zeroed
|
| Andrew Price (3):
| gfs2: Add a next-resource-group pointer to resource groups
| gfs2: Add rindex fields to rgrp headers
| gfs2: Add a crc field to resource group headers
|
| fs/gfs2/rgrp.c | 16 +++++++++++++++-
| include/uapi/linux/gfs2_ondisk.h | 15 ++++++++++++---
| 2 files changed, 27 insertions(+), 4 deletions(-)
|
| --
| 2.13.6
Hi,
Thanks. All three patches are now pushed to the for-next branch of the linux-gfs2 tree:
gfs2: Add a next-resource-group pointer to resource groups
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=65adc27375a85beb57c3869cedb2a410fad9c288
gfs2: Add rindex fields to rgrp headers
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=166725d96322473305e35f9d580591a01697ab29
gfs2: Add a crc field to resource group headersfor-next
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=850d2d915fa69011bef9bd668499cce889fdd8b3
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2017-12-12 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 14:59 [Cluster-devel] [PATCH v2 0/3] gfs2: Add new resource group header fields Andrew Price
2017-12-08 14:59 ` [Cluster-devel] [PATCH v2 1/3] gfs2: Add a next-resource-group pointer to resource groups Andrew Price
2017-12-08 14:59 ` [Cluster-devel] [PATCH v2 2/3] gfs2: Add rindex fields to rgrp headers Andrew Price
2017-12-08 14:59 ` [Cluster-devel] [PATCH v2 3/3] gfs2: Add a crc field to resource group headers Andrew Price
2017-12-08 15:14 ` [Cluster-devel] [PATCH v2 0/3] gfs2: Add new resource group header fields Bob Peterson
2018-01-28 21:25 ` Andrew Price
2018-01-29 13:30 ` Bob Peterson
2018-01-29 13:44 ` Andrew Price
2017-12-12 18:00 ` Bob Peterson [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=1271599422.40834307.1513101618014.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.