From: jim owens <jowens@hp.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Hot topics for the next release
Date: Wed, 06 Aug 2008 16:36:30 -0400 [thread overview]
Message-ID: <489A0B4E.6010809@hp.com> (raw)
In-Reply-To: <1218040611.15342.92.camel@think.oraclecorp.com>
Chris Mason wrote:
> Josef's allocator fix is on the list because we currently fall over in
> some workloads at 100% cpu time when the FS is 60% full. The space
> indexing is complex and strange, it just needs to be redone.
I don't understand. Do you mean josef wants someone to fix
multithreading or do you mean he is doing that as part of
an allocator fix he is working on, or did you mean that
his work is an exception and you really were not looking at
doing any allocator changes?
I see this in your 0.16 list:
> Better in-memory free space indexing (Josef)
but did not tie it to the allocator. Is that it?
and I'll add an area I missed before in the Development_timeline:
- Fallocate support (at least disk format level)
as part of the allocator bundle-of-too-much-work :)
jim
next prev parent reply other threads:[~2008-08-06 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:21 Hot topics for the next release Chris Mason
2008-08-06 14:58 ` David Woodhouse
2008-08-06 15:13 ` Chris Mason
2008-08-06 15:26 ` Toei Rei
2008-08-06 18:45 ` David Woodhouse
2008-08-06 15:42 ` jim owens
2008-08-06 16:36 ` Chris Mason
2008-08-06 20:36 ` jim owens [this message]
2008-08-06 20:43 ` Chris Mason
2008-08-06 20:49 ` Joe Peterson
2008-08-06 20:53 ` 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=489A0B4E.6010809@hp.com \
--to=jowens@hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox