From: Mark Goodwin <markgw@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH, needs a new owner] XFS multi-buftarg
Date: Thu, 12 Feb 2009 15:05:38 +1100 [thread overview]
Message-ID: <4993A012.5060008@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Series of 10 patches, originally by Dave Chinner. This series
is unfinished, or needs forward porting to top-of-tree at the
very least. The feature implements some allocator/layout optimizations
by grouping AGs based on concat units, I think ;-)
01/10 xfs-concat-unit
02/10 xfs-factor-pag-freelist-check-2
03/10 xfs-pnb-per-node-buftargs
04/10 xfs-pnb-trans-read-no-dev
05/10 xfs-pnb-read-buf-no-dev
06/10 xfs-pnb-connect-ags-to-legs
07/10 xfs-pnb-perag-debug-update
08/10 xfs-pnb-fix-growfs
09/10 xfs-pnb-log-recovery-targ
10/10 xfs-pnb-ddev-buf-item-asserts
[-- Attachment #2: patches.multi-buftarg.tgz --]
[-- Type: application/octet-stream, Size: 45161 bytes --]
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-02-12 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 4:05 Mark Goodwin [this message]
2009-02-19 19:23 ` [PATCH, needs a new owner] XFS multi-buftarg Christoph Hellwig
2009-02-19 23:58 ` Dave Chinner
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=4993A012.5060008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox