From: jim owens <jowens@hp.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs conf call
Date: Thu, 28 Aug 2008 13:44:38 -0400 [thread overview]
Message-ID: <48B6E406.6010906@hp.com> (raw)
In-Reply-To: <f058a9c30808280614p74763300g21a1102676b81dd6@mail.gmail.com>
Call summary:
Chris has been rewriting fsync to improve performance
- 10X better multi-threaded scaling for regular files
- directory fsync performance has not been addressed
Ric noted that Josef's fine-granularity timer work
in the main line could boost btrfs fsync performance.
Eric has seen single stream write performance drop
after v.15, his runs indicate allocator-induced stalls.
Josef is working on allocator fix round 3... round 2 had
regressions in some benchmarks. Chris proposed he try a
design midway between the round 1 and round 2 code.
Eric noted build problems with older kernels (2.16.18 ?)
because of the btrfs NFS patch... needs volunteer to fix.
Eric and Chris discussed testing using some of the xfs
tests without using the complete harness suite.
More plumber's conference discussion, Chris's btrfs talk
will be fairly high level (as expected given where we are).
Attendance is expected to be good on all days including
the last day (so if I go, I won't leave early). How to
set up the filesystem BOF is pending plumber's site update.
next prev parent reply other threads:[~2008-08-28 17:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 13:21 Btrfs conf call Chris Mason
2008-08-28 13:14 ` Miguel Sousa Filipe
2008-08-28 17:44 ` jim owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 13:08 Btrfs Conf call Chris Mason
2009-04-01 13:14 Btrfs Conf Call Chris Mason
2009-03-18 14:23 Btrfs conf call Chris Mason
2009-03-04 13:59 Chris Mason
2009-02-18 1:20 Btrfs Conf Call Chris Mason
2008-11-19 1:03 Btrfs Conf call Chris Mason
2008-11-05 1:20 Chris Mason
2008-09-10 15:29 Btrfs conf call Chris Mason
2008-09-16 19:05 ` jj
2008-09-16 19:31 ` Jeff Schroeder
2008-09-16 20:03 ` Eric Anopolsky
2008-08-13 16:33 Chris Mason
2008-08-13 17:46 ` Morey Roof
2008-08-13 20:22 ` jim owens
2008-08-13 21:02 ` Morey Roof
2008-08-13 21:30 ` jim owens
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=48B6E406.6010906@hp.com \
--to=jowens@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox