public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [RFC v4 0/2] xfs: automatic relogging experiment
Date: Thu,  5 Dec 2019 12:50:35 -0500	[thread overview]
Message-ID: <20191205175037.52529-1-bfoster@redhat.com> (raw)

Hi all,

Here's a v4 RFC for automatic relogging and probably the closest one IMO
to a non-RFC worthy implementation. There's still a few kinks, but this
might be the right combination of simplicity, effectiveness and
flexibility for future enhancement. Patch 1 adds the mechanism and patch
2 uses it for the quotaoff start intent. See the commit logs for further
details. 

Thoughts, reviews, flames appreciated.

Brian

rfcv4:
- AIL based approach.
rfcv3: https://lore.kernel.org/linux-xfs/20191125185523.47556-1-bfoster@redhat.com/
- CIL based approach.
rfcv2: https://lore.kernel.org/linux-xfs/20191122181927.32870-1-bfoster@redhat.com/
- Different approach based on workqueue and transaction rolling.
rfc: https://lore.kernel.org/linux-xfs/20191024172850.7698-1-bfoster@redhat.com/

Brian Foster (2):
  xfs: automatic log item relog mechanism
  xfs: automatically relog the quotaoff start intent

 fs/xfs/xfs_dquot_item.c  |  7 +++++
 fs/xfs/xfs_qm_syscalls.c |  9 +++++++
 fs/xfs/xfs_trace.h       |  1 +
 fs/xfs/xfs_trans.c       | 30 +++++++++++++++++++++
 fs/xfs/xfs_trans.h       |  7 ++++-
 fs/xfs/xfs_trans_ail.c   | 56 ++++++++++++++++++++++++++++++++++++++--
 fs/xfs/xfs_trans_priv.h  |  5 ++++
 7 files changed, 112 insertions(+), 3 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-12-05 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 17:50 Brian Foster [this message]
2019-12-05 17:50 ` [RFC v4 1/2] xfs: automatic log item relog mechanism Brian Foster
2019-12-05 21:02   ` Dave Chinner
2019-12-06 14:56     ` Brian Foster
2019-12-05 17:50 ` [RFC v4 2/2] xfs: automatically relog the quotaoff start intent Brian Foster

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=20191205175037.52529-1-bfoster@redhat.com \
    --to=bfoster@redhat.com \
    --cc=linux-xfs@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