All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:42:04 -0400	[thread overview]
Message-ID: <4899C64C.2040107@hp.com> (raw)
In-Reply-To: <1218032511.15342.73.camel@think.oraclecorp.com>

> Improved allocator threading

I wanted to work on the allocator with a larger scope
where threading is only a minor part of trying to address
these items from the Project_ideas that I think could change
disk format in some way (to fix it before v1.0):
  - Different sector sizes
  - Multiple chunk trees and extent allocation trees
  - Limiting btree failure domains
and maybe impacting this from Development_timeline
   - Reserved space for online fsck and the ability to add
     storage so that a background extent allocation check can proceed

Maybe this is too ambitious or I am seeing intersections that
are not there, but I am prepared to try doing the allocator.

jim

P.S.  Are there other V1.0 format issues to lock down that
should be worked before the missing features like O_DIRECT?

  parent reply	other threads:[~2008-08-06 15:42 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 [this message]
2008-08-06 16:36   ` Chris Mason
2008-08-06 20:36     ` jim owens
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=4899C64C.2040107@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 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.