From: Ric Wheeler <ricwheeler@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
Chris Mason <chris.mason@oracle.com>, jim owens <jowens@hp.com>,
Andi Kleen <andi@firstfloor.org>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs_tree_lock & trylock
Date: Mon, 08 Sep 2008 13:32:14 -0400 [thread overview]
Message-ID: <48C5619E.9010505@gmail.com> (raw)
In-Reply-To: <20080908171742.GB19117@infradead.org>
Christoph Hellwig wrote:
> On Mon, Sep 08, 2008 at 09:49:42AM -0700, Stephen Hemminger wrote:
>
>> Not to mention the problem that developers seem to have faster machines than
>> average user, but slower than the enterprise and future generation CPU's.
>> So any tuning value seems to get out of date fast.
>>
>
> So where do my fellow developers get these fast systems from? :)
>
>
Actually, my experience is that most linux file system developers have
really poking, aged hardware with little to no cutting edge storage (or
even cutting edge commercial class storage). Testing file systems on lap
tops and desktops with old CPUs, no DRAM and 40GB drives does not even
reflect a typical home user these days :-)
ric
next prev parent reply other threads:[~2008-09-08 17:32 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
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 [this message]
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=48C5619E.9010505@gmail.com \
--to=ricwheeler@gmail.com \
--cc=andi@firstfloor.org \
--cc=chris.mason@oracle.com \
--cc=hch@infradead.org \
--cc=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shemminger@vyatta.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