All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Chandan Babu R <chandan.babu@oracle.com>,
	linux-xfs@vger.kernel.org, Dave Chinner <dchinner@redhat.com>
Subject: Re: [PATCH 11/11] xfs: skip flushing log items during push
Date: Wed, 3 Jul 2024 09:29:47 +1000	[thread overview]
Message-ID: <ZoSNa2NkSVKb3ecl@dread.disaster.area> (raw)
In-Reply-To: <20240702185120.GL612460@frogsfrogsfrogs>

On Tue, Jul 02, 2024 at 11:51:20AM -0700, Darrick J. Wong wrote:
> On Fri, Jun 21, 2024 at 10:46:45AM -0700, Darrick J. Wong wrote:
> > On Fri, Jun 21, 2024 at 07:48:08AM +0200, Christoph Hellwig wrote:
> > > On Thu, Jun 20, 2024 at 12:51:42PM -0700, Darrick J. Wong wrote:
> > > > > Further with no backoff we don't need to gather huge delwri lists to
> > > > > mitigate the impact of backoffs, so we can submit IO more frequently
> > > > > and reduce the time log items spend in flushing state by breaking
> > > > > out of the item push loop once we've gathered enough IO to batch
> > > > > submission effectively.
> > > > 
> > > > Is that what the new count > 1000 branch does?
> > > 
> > > That's my interpreation anyway.  I'll let Dave chime in if he disagrees.

Yes, that's correct. I didn't finish this patch - I never wrote the
comments in the code to explain this because I don't bother doing
that until I've validated the heuristic and know it mostly works
as desired. I simply hadn't closed the loop.

Please add comments to the code to explain what the magic "1000"
is...

> > <nod> I'll await a response on this...
> 
> <shrug> No response after 11 days, I'll not hold this up further over a
> minor point.

I've been on PTO for the last couple of weeks, and I'm still
catching up on email. You could have just pinged me on #xfs asking
if I'd seen this, just like jlayton did about the mgtime stuff last
week. I answered even though I was on PTO. You always used to do
this when you wanted an answer to a question - I'm curious as to why
have you stopped using #xfs to ask questions about code, bugs and
patch reviews?

-Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2024-07-02 23:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  7:21 xfs: byte-based grant head reservation tracking v4 Christoph Hellwig
2024-06-20  7:21 ` [PATCH 01/11] xfs: fix the contact address for the sysfs ABI documentation Christoph Hellwig
2024-06-20 15:20   ` Darrick J. Wong
2024-06-20  7:21 ` [PATCH 02/11] xfs: move and rename xfs_trans_committed_bulk Christoph Hellwig
2024-06-20  7:21 ` [PATCH 03/11] xfs: AIL doesn't need manual pushing Christoph Hellwig
2024-06-20 19:01   ` Darrick J. Wong
2024-06-20  7:21 ` [PATCH 04/11] xfs: background AIL push should target physical space Christoph Hellwig
2024-06-20 19:42   ` Darrick J. Wong
2024-06-21  5:37     ` Christoph Hellwig
2024-06-21 16:18       ` Darrick J. Wong
2024-06-20  7:21 ` [PATCH 05/11] xfs: ensure log tail is always up to date Christoph Hellwig
2024-06-20  7:21 ` [PATCH 06/11] xfs: l_last_sync_lsn is really AIL state Christoph Hellwig
2024-06-20  7:21 ` [PATCH 07/11] xfs: collapse xlog_state_set_callback in caller Christoph Hellwig
2024-06-20  7:21 ` [PATCH 08/11] xfs: track log space pinned by the AIL Christoph Hellwig
2024-06-20  7:21 ` [PATCH 09/11] xfs: pass the full grant head to accounting functions Christoph Hellwig
2024-06-20  7:21 ` [PATCH 10/11] xfs: grant heads track byte counts, not LSNs Christoph Hellwig
2024-07-01  0:59   ` Dave Chinner
2024-06-20  7:21 ` [PATCH 11/11] xfs: skip flushing log items during push Christoph Hellwig
2024-06-20 19:51   ` Darrick J. Wong
2024-06-21  5:48     ` Christoph Hellwig
2024-06-21 17:46       ` Darrick J. Wong
2024-07-02 18:51         ` Darrick J. Wong
2024-07-02 23:29           ` Dave Chinner [this message]
2024-07-03  5:10             ` Darrick J. Wong

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=ZoSNa2NkSVKb3ecl@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=chandan.babu@oracle.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --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 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.