From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: reduce lock traffic on incore sb lock
Date: Wed, 29 Sep 2010 02:13:51 -0400 [thread overview]
Message-ID: <20100929061351.GA20921@infradead.org> (raw)
In-Reply-To: <20100929055748.GK5665@dastard>
On Wed, Sep 29, 2010 at 03:57:48PM +1000, Dave Chinner wrote:
> FWIW, I've got a prototype that converts the per-cpu counters to the
> generic per-cpu counter infrastructure. It chops out almost all the
> xfs_icsb_* stuff (including xfs_icsb_modify_counters()) and has a
> diffstat of:
Sounds good - I always throught of the balanced per-cpu counters as
infrastructure that really shouldn't sit inside XFS.
> It needs a significant cleanup of xfs_mod_incore_sb() before/after
> the conversion which I haven't done yet because I haven't quite got
> my new percpu_counter_test_and_add_delta() function working
> correctly yet. I spotted this locking problem when testing the
> patch...
>
> That said, there's no reason why my percpu counter code needs to run
> through xfs_mod_incore_sb() at all. If we have a separate path for
> per-cpu counters then I can rework my code on top of that....
We'll always need a low-level function to to the actual superblock
updates and a high-level one modifying the per-cpu counters. I don't
think the exact naming matters too much.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-29 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 0:51 [PATCH] xfs: reduce lock traffic on incore sb lock Dave Chinner
2010-09-29 4:04 ` Christoph Hellwig
2010-09-29 5:57 ` Dave Chinner
2010-09-29 6:13 ` Christoph Hellwig [this message]
2010-09-29 6:28 ` Dave Chinner
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=20100929061351.GA20921@infradead.org \
--to=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox