All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Leckie <pleckie@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] XFS: don't block in xfs_qm_dqflush() during async writeback
Date: Fri, 10 Oct 2008 11:16:06 +1000	[thread overview]
Message-ID: <48EEACD6.7070805@sgi.com> (raw)
In-Reply-To: <1223416677-8458-1-git-send-email-david@fromorbit.com>

Dave Chinner wrote:
> Normally dquots are written back via delayed write mechanisms.  They
> are flushed to their backing buffer by xfssyncd, which is then
> pushed out by either AIL or xfsbufd flushing. The flush from the
> xfssyncd is supposed to be non-blocking, but xfs_qm_dqflush() always
> waits for pinned duots, which means that it will block for the
> length of time it takes to do a synchronous log force. This causes
> unnecessary extra log I/O to be issued whenever we try to flush a
> busy dquot.
>
> Avoid the log forces and blocking xfssyncd by making xfs_qm_dqflush()
> pay attention to what type of sync it is doing when it sees a pinned
> dquot and not waiting when doing non-blocking flushes.
>   
This patch looks good.

Thanks,
Pete

      reply	other threads:[~2008-10-10  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 21:57 [PATCH] XFS: don't block in xfs_qm_dqflush() during async writeback Dave Chinner
2008-10-10  1:16 ` Peter Leckie [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=48EEACD6.7070805@sgi.com \
    --to=pleckie@sgi.com \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.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.