From: jim owens <jowens@hp.com>
To: Morey Roof <moreyroof@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs conf call
Date: Wed, 13 Aug 2008 16:22:52 -0400 [thread overview]
Message-ID: <48A3429C.5040000@hp.com> (raw)
In-Reply-To: <48A31DEA.5090903@gmail.com>
Morey Roof wrote:
> Could someone write a quick recap of this for those of us who are
> interested and happened to miss it?
Everyone on the call seems to be waiting for someone else
to respond. I'll do it just to make up for dedup :)
- Chris said he saw major performance problems from pdflush
and he is currently working on a btrfs thread to fix this.
- Eric has been testing v0.16 single-stream-write performance
and is seeing kswapd issues (also part of Chris's fix)
and will take Chris's code as soon as it is ready.
- Josef is rewriting the in-memory extent allocator to make
it perform much better and will also fix multithreading.
- Ming Ming and Chris will try to arrange a general
breakout session for all filesystems at the plumber's
conference in september. (Chris is presenting a talk
on btrfs at the conference)
- I listened and contributed only this synopsis.
jim
next prev parent reply other threads:[~2008-08-13 20:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 16:33 Btrfs conf call Chris Mason
2008-08-13 17:46 ` Morey Roof
2008-08-13 20:22 ` jim owens [this message]
2008-08-13 21:02 ` Morey Roof
2008-08-13 21:30 ` jim owens
-- strict thread matches above, loose matches on Subject: below --
2008-08-27 13:21 Chris Mason
2008-08-28 13:14 ` Miguel Sousa Filipe
2008-08-28 17:44 ` jim owens
2008-09-10 15:29 Chris Mason
2008-09-16 19:05 ` jj
2008-09-16 19:31 ` Jeff Schroeder
2008-09-16 20:03 ` Eric Anopolsky
2008-11-05 1:20 Btrfs Conf call Chris Mason
2008-11-19 1:03 Chris Mason
2009-02-18 1:20 Btrfs Conf Call Chris Mason
2009-03-04 13:59 Btrfs conf call Chris Mason
2009-03-18 14:23 Chris Mason
2009-04-01 13:14 Btrfs Conf Call Chris Mason
2009-04-15 13:08 Btrfs Conf call 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=48A3429C.5040000@hp.com \
--to=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moreyroof@gmail.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