All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH, needs a new owner] XFS Alloc Policies
Date: Thu, 12 Feb 2009 15:03:28 +1100	[thread overview]
Message-ID: <49939F90.20905@sgi.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]


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:

01/18 xfs-fix-buf-trace
02/18 xfs-kconfig-debug
03/18 xfs-ap-inode-ag-hooks
04/18 xfs-ap-inode-agi-search-hooks
05/18 xfs-ap-data-hooks
06/18 xfs-ap-data-ac-context
07/18 xfs-ap-make-it-work
08/18 xfs-ap-per-inode-policy
09/18 xfs-ap-policy-register
10/18 xfs-ap-per-fs-policy
11/18 xfs-ap-ioctl-interface
12/18 xfs-sysfs-mount-t
13/18 xfs-ap-kobj-core
14/18 xfs-ap-handle-growfs-past-1TB
15/18 xfs-ap-cleanup-data-fallback
16/18 xfs-ap-propagate-context
17/18 xfs-ap-fix-filestreams
18/18 xfs-ap-split-inode-policy-id


[-- Attachment #2: patches.alloc-policy.tgz --]
[-- Type: application/octet-stream, Size: 138841 bytes --]

[-- Attachment #3: Type: text/plain, Size: 121 bytes --]

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

             reply	other threads:[~2009-02-12  4:04 UTC|newest]

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

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=49939F90.20905@sgi.com \
    --to=markgw@sgi.com \
    --cc=goodwinos@gmail.com \
    --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 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.