From: Andi Kleen <andi@firstfloor.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs_tree_lock & trylock
Date: Mon, 8 Sep 2008 15:54:14 +0200 [thread overview]
Message-ID: <20080908135414.GG26079@one.firstfloor.org> (raw)
In-Reply-To: <1220881666.8537.3.camel@think.oraclecorp.com>
> The idea is to try to spin for a bit to avoid scheduling away, which is
> especially important for the high levels. Most holders of the mutex
> let it go very quickly.
Ok but that surely should be implemented in the general mutex code then
or at least in a standard adaptive mutex wrapper?
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-09-08 13:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 11:10 btrfs_tree_lock & trylock Andi Kleen
2008-09-08 13:47 ` Chris Mason
2008-09-08 13:54 ` Andi Kleen [this message]
2008-09-08 14:02 ` Chris Mason
2008-09-08 14:20 ` Andi Kleen
2008-09-08 15:07 ` Stephen Hemminger
2008-09-08 15:28 ` Chris Mason
2008-09-08 23:26 ` Steve Long
2008-09-08 15:47 ` Andi Kleen
2008-09-08 15:50 ` Stephen Hemminger
2008-09-08 15:55 ` Chris Mason
2008-09-08 16:13 ` jim owens
2008-09-08 16:20 ` Chris Mason
2008-09-08 16:49 ` Stephen Hemminger
2008-09-08 17:17 ` Christoph Hellwig
2008-09-08 17:32 ` Ric Wheeler
2008-09-08 23:28 ` Steve Long
2008-09-08 17:16 ` adaptive mutexes, was " 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=20080908135414.GG26079@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.