From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Recording extents in GFS2
Date: Thu, 25 Feb 2021 14:45:25 -0500 (EST) [thread overview]
Message-ID: <578920647.58334818.1614282325621.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAHc6FU6xpZJmuX2gQB9qrOGg+Cnh=OSUVrij9G6vQmn9nDaC7Q@mail.gmail.com>
----- Original Message -----
> On Thu, Feb 25, 2021 at 7:48 PM Bob Peterson <rpeterso@redhat.com> wrote:
>
> > ----- Original Message -----
> > > >> once we change the journal format, in addition to recording block
> > numbers
> > > >> as extents, there are some additional issues we should address at the
> > same
> > > >> time:
> >
> > One thing I've always thought we should improve upon was the way we manage
> > our bitmaps. Right now, if you allocate or free a block, unless it's on the
> > first block of the rgrp, we need to write two blocks: (1) One for the
> > bitmap
> > that needs to change and, (2) Another for the rgrp to adjust its allocated
> > and
> > free numbers. The rgrplvb code will make this faster, but it would be nice
> > if
> > we would somehow keep "version 2" bitmaps such that each keeps its own
> > statistics.
> >
> > That way we only need to journal and write the affected bitmap, and not
> > necessarily its rgrp block as well. I could see us keep separate glocks
> > for each bitmap, for example, and allowing multiple nodes to work on the
> > same portion of the file system, but on unique bitmaps.
> >
>
> On the other hand, we currently only need to look at the first block of
> each resource group to figure out if a resource group is suitable for an
> allocation. If we move that information into the bitmap blocks, we'll have
> to look at each of those blocks instead. That's not going to improve our
> performance.
>
> Andreas
>
The LVBs will shield us from that, but they won't shield us from having
to rewrite 2 blocks instead of 1.
Bob
next prev parent reply other threads:[~2021-02-25 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 16:38 [Cluster-devel] Recording extents in GFS2 Abhijith Das
2020-12-14 10:46 ` Steven Whitehouse
2021-01-24 6:44 ` Abhijith Das
2021-02-02 15:08 ` Bob Peterson
2021-02-02 17:35 ` Steven Whitehouse
2021-02-20 9:48 ` Andreas Gruenbacher
2021-02-22 10:20 ` Steven Whitehouse
2021-02-22 11:41 ` Andreas Gruenbacher
2021-02-22 13:03 ` Andreas Gruenbacher
2021-02-25 18:48 ` Bob Peterson
2021-02-25 19:08 ` Andreas Gruenbacher
2021-02-25 19:45 ` Bob Peterson [this message]
2021-03-01 17:53 ` Andreas Gruenbacher
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=578920647.58334818.1614282325621.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 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).