cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 07/12] gfs2: make gfs2_ail1_empty_one return the count of active items
Date: Thu, 27 Aug 2020 12:45:55 -0400 (EDT)	[thread overview]
Message-ID: <669703327.14508047.1598546755636.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAHc6FU4yVZwgK7966J+Op=6Y3cCFFPe9uQ16x5u_xZ3zs=fhkg@mail.gmail.com>

----- Original Message -----
> Hi Bob,
> 
> On Fri, Aug 21, 2020 at 7:33 PM Bob Peterson <rpeterso@redhat.com> wrote:
> > This patch is one baby step toward simplifying the journal management.
> > It simply changes function gfs2_ail1_empty_one from a void to an int and
> > makes it return a count of active items. This allows the caller to check
> > the return code rather than list_empty on the tr_ail1_list. This way
> > we can, in a later patch, combine transaction ail1 and ail2 lists.
> 
> what does "we can combine transaction ail1 and ail2 lists" mean?

Hi Andreas,

Well, I've been looking into ways we can simplify the journal logging
code to give us more throughput. One way is to reduce the number of
calls to lock the ail lists. Right now we lock the sd_ail_lock spin_lock
when we add items to the ail1, move them from ail1 to ail2, and for
processing the items on ail2. If we had one combined "ail_list" rather
than two (ail1 and ail2) we wouldn't need to move items from list to list.
We could instead just flag the bufdata elements (somehow--like set_bit
and clear_bit) which could allow us to grab that spin_lock less often,
leading to better throughput. This in turn might lead us to other
simplifications.

Bob Peterson



  reply	other threads:[~2020-08-27 16:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 17:33 [Cluster-devel] [GFS2 PATCH 00/12] gfs2: jdata patch collection revisited Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 01/12] gfs2: rename gfs2_write_full_page to gfs2_write_jdata_page, remove parm Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 02/12] gfs2: add missing log_blocks trace points in gfs2_write_revokes Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 03/12] gfs2: enhance log_blocks trace point to show log blocks free Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 04/12] gfs2: Wipe jdata and ail1 in gfs2_journal_wipe, formerly gfs2_meta_wipe Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 05/12] gfs2: Calculate number of revokes during evict Bob Peterson
2020-08-27  6:00   ` Andreas Gruenbacher
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 06/12] gfs2: Create transaction for inodes with i_nlink != 0 Bob Peterson
2020-08-27  6:00   ` Andreas Gruenbacher
2020-08-27  7:41     ` Steven Whitehouse
2020-08-27 13:00     ` Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 07/12] gfs2: make gfs2_ail1_empty_one return the count of active items Bob Peterson
2020-08-27  6:00   ` Andreas Gruenbacher
2020-08-27 16:45     ` Bob Peterson [this message]
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 08/12] gfs2: don't lock sd_ail_lock in gfs2_releasepage Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 09/12] gfs2: Only set PageChecked if we have a transaction Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 10/12] gfs2: simplify gfs2_block_map Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 11/12] gfs2: Ignore journal log writes for jdata holes Bob Peterson
2020-08-21 17:33 ` [Cluster-devel] [GFS2 PATCH 12/12] gfs2: add some much needed cleanup for log flushes that fail Bob Peterson

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=669703327.14508047.1598546755636.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).