From: Andi Kleen <andi@firstfloor.org>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com
Subject: Re: PARTIAL TAKE 964999 - lazy superblock counters for XFS
Date: 24 May 2007 23:48:16 +0200 [thread overview]
Message-ID: <p73wsyxdhb3.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070522075932.E665058CA531@chook.melbourne.sgi.com>
dgc@sgi.com (David Chinner) writes:
>
> The key to removing the contention is to not require the superblock
> fields in question to be locked. We do that by not marking the
> superblock dirty in the transaction. IOWs, we modify the incore
> superblock but do not modify the cached superblock buffer. In short,
> we do not log superblock modifications to critical fields in the
> superblock on every transaction. In fact we only do it just before
> we write the superblock to disk every sync period or just before
> unmount.
Does this mean it will increases performance on small systems too
due to less super block writes or is it purely for large
system scalability?
-Andi
next prev parent reply other threads:[~2007-05-24 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 7:59 PARTIAL TAKE 964999 - lazy superblock counters for XFS David Chinner
2007-05-24 21:48 ` Andi Kleen [this message]
2007-05-24 23:24 ` David Chinner
2007-05-25 6:53 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2007-05-22 8:04 David 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=p73wsyxdhb3.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=dgc@sgi.com \
--cc=sgi.bugs.xfs@engr.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