public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <goodwinos@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, needs a new owner] XFS Alloc Policies
Date: Mon, 16 Feb 2009 11:08:17 +1100	[thread overview]
Message-ID: <4998AE71.2040304@gmail.com> (raw)
In-Reply-To: <20090212185853.GA23056@infradead.org>

Christoph Hellwig wrote:
> On Thu, Feb 12, 2009 at 03:03:28PM +1100, Mark Goodwin wrote:
>> Series of patches, originally by Dave Chinner. This series
>> of 18 patches is unfinished and needs a new owner - the
>> feature partially implements pluggable allocation policies
>> for XFS.
>>
>> A fairly substantial architectural write-up with community
>> debate/feedback on the design would be appropriate before
>> embarking on this. Tarball attached for the following:
> 
> Thanks for posting these.  I'm pretty sure these patches will
> get some sort of makeover before beeing ready, but they are
> an important building block for some of the interesting work
> we're planning to do (like the multi device work or ssd-aware
> allocators), so there will be some action on it.
> 

Yep. It would be good if there was some kind of write-up on
those plans since the feature will be fairly intrusive. I assume
it's been a back-of-the-envelope-with-beer kind of discussion
so far ..

Cheers
-- Mark

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2009-02-16  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  4:03 [PATCH, needs a new owner] XFS Alloc Policies Mark Goodwin
2009-02-12 18:58 ` Christoph Hellwig
2009-02-16  0:08   ` Mark Goodwin [this message]

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=4998AE71.2040304@gmail.com \
    --to=goodwinos@gmail.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.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