public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: David Chinner <dgc@sgi.com>, xfs-oss <xfs@oss.sgi.com>,
	xfs-dev <xfs-dev@sgi.com>
Subject: Re: [PATCH, RFC] Move AIL pushing into a separate thread
Date: Fri, 9 Nov 2007 14:16:55 +1100	[thread overview]
Message-ID: <20071109031655.GQ66820511@sgi.com> (raw)
In-Reply-To: <4733AB27.70208@sgi.com>

On Fri, Nov 09, 2007 at 11:34:47AM +1100, Lachlan McIlroy wrote:
> I like the sound of this Dave.  I'm still going through the code in
> detail.
> 
> Could we convert the ail lock into a mutex to ease the load?  I know
> it may not improve throughput but it would at least relieve the CPUs
> to do other stuff.

Most of the time the ail lock is used for very short periods of
time, (e.g.  less than ten lines of code) so a spin lock is
appropriate. What we are seeing here is too many CPUs holding it for
to long trying to do the work one CPU could easily do.

i.e. the bug we are seeing here is the contention on the lock, not
the type of lock. If we change to a sleeping lock, all ppl will see
is a slowdown and that is much, much harder to diagnose on a
production system than spin lock contention....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-11-09  3:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05  5:07 [PATCH, RFC] Move AIL pushing into a separate thread David Chinner
2007-11-09  0:34 ` Lachlan McIlroy
2007-11-09  3:16   ` David Chinner [this message]
2007-11-15  3:32 ` Lachlan McIlroy
2007-11-16  0:43   ` David Chinner
2007-11-16  1:19     ` Lachlan McIlroy
2007-11-16  7:23     ` Christoph Hellwig

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=20071109031655.GQ66820511@sgi.com \
    --to=dgc@sgi.com \
    --cc=lachlan@sgi.com \
    --cc=xfs-dev@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox