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>,
	Klaus Strebel <klaus.strebel@gmx.net>,
	xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: Review: Reduce in-core superblock lock contention near ENOSPC
Date: Fri, 8 Dec 2006 16:16:29 +1100	[thread overview]
Message-ID: <20061208051629.GV33919298@melbourne.sgi.com> (raw)
In-Reply-To: <457682C3.6000802@sgi.com>

On Wed, Dec 06, 2006 at 08:43:47AM +0000, Lachlan McIlroy wrote:
> David Chinner wrote:
> >On Tue, Dec 05, 2006 at 12:46:46PM +0100, Klaus Strebel wrote:
> >
> >>Hi guys,
> >>
> >>just updated my CVS copy from oss.sgi.com ( the linux-2.6-xfs ) and 
> >>tried to compile ... but your patch failes to compile if HAVE_PERCPU_SB 
> >>is #ifndef'd :-(, the m_icsb_mutex is not in the struct see xfs_mount.h. 
> >>Make oldconfig didn't show HAVE_PERCPU_SB as option for .config, looks 
> >>like nobody tested on a single processor config ??
> >
> >
> >Sorry - my bad. The code did not change for UP, so I didn't think to
> >test it.  The patch below abstracts the icsb_mutex so that it
> >doesn't get directly referenced by code outside the per-cpu counter
> >code. Builds with and without HAVE_PERCPU_SB defined.
> >
> >I'll run a test cycle on it and get it fixed up.
> >
> >Cheers,
> >
> >Dave.
> 
> @@ -1803,6 +1803,7 @@ xfs_icsb_destroy_counters(
>  		unregister_hotcpu_notifier(&mp->m_icsb_notifier);
>  		free_percpu(mp->m_sb_cnts);
>  	}
> +	mutex_destroy(&mp->m_icsb_mutex);
>  }
> 
> Do you need to abstract the call to mutex_destroy too?

No. I didn't abstract the mutex_init and mutex_destroy calls because
they are in the init/destroy functions for the icsb subsystem and
those functions are #define'd out when HAVE_PERCPU_SB is not
defined.

> The rest of the change looks good.

Thanks, Lachlan.

Cheers,

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

      reply	other threads:[~2006-12-08  5:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23  4:41 Review: Reduce in-core superblock lock contention near ENOSPC David Chinner
2006-11-30 18:03 ` Lachlan McIlroy
2006-11-30 22:38   ` David Chinner
2006-12-01  0:41     ` David Chinner
2006-12-01 20:12       ` Lachlan McIlroy
2006-12-01 19:22     ` Lachlan McIlroy
2006-12-03 23:49       ` David Chinner
2006-12-05 11:46         ` Klaus Strebel
2006-12-05 21:55           ` David Chinner
2006-12-06  8:43             ` Lachlan McIlroy
2006-12-08  5:16               ` David Chinner [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=20061208051629.GV33919298@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=klaus.strebel@gmx.net \
    --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