linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH RFC] btrfs: Simplify locking
Date: Tue, 22 Mar 2011 19:13:09 -0400	[thread overview]
Message-ID: <1300835390-sup-7485@think> (raw)
In-Reply-To: <20110321181124.GK12003@htj.dyndns.org>

Excerpts from Tejun Heo's message of 2011-03-21 14:11:24 -0400:
> Hello,
> 
> On Mon, Mar 21, 2011 at 01:24:37PM -0400, Chris Mason wrote:
> > Very interesting.  Ok, I'll definitely rerun my benchmarks as well.  I
> > used dbench extensively during the initial tuning, but you're forcing
> > the memory low in order to force IO.
> > 
> > This case doesn't really hammer on the locks, it hammers on the
> > transition from spinning to blocking.  We want also want to compare
> > dbench entirely in ram, which will hammer on the spinning portion.
> 
> Here's re-run of DFL and SIMPLE with the memory restriction lifted.
> Memory is 4GiB and disk remains mostly idle with all CPUs running
> full.
> 
>        USER   SYSTEM   SIRQ    CXTSW  THROUGHPUT
> DFL    59898  504517    377  6814245     782.295
> SIMPLE 61090  493441    457  1631688     827.751
>     
> So, about the same picture.

Ok, this impact of this is really interesting.  If we have very short
waits where there is no IO at all, this patch tends to lose.  I ran with
dbench 10 and got about 20% slower tput.

But, if we do any IO at all it wins by at least that much or more.  I
think we should take this patch and just work on getting rid of the
scheduling with the mutex held where possible.

Tejun, could you please send the mutex_tryspin stuff in?  If we can get
a sob for that I can send the whole thing.

-chris

  reply	other threads:[~2011-03-22 23:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20 17:44 [PATCH RFC] btrfs: Simplify locking Tejun Heo
2011-03-20 19:56 ` Tejun Heo
2011-03-20 20:17   ` Tejun Heo
2011-03-21  0:10 ` Chris Mason
2011-03-21  8:29   ` Tejun Heo
2011-03-21 16:59     ` Tejun Heo
2011-03-21 17:11       ` Tejun Heo
2011-03-21 17:24       ` Chris Mason
2011-03-21 18:11         ` Tejun Heo
2011-03-22 23:13           ` Chris Mason [this message]
2011-03-23 10:46             ` Tejun Heo
2011-03-23 11:44               ` Chris Mason

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=1300835390-sup-7485@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tj@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).