From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, needs new owner] xfs_repair memory optimization
Date: Sat, 24 Jan 2009 09:23:31 -0500 [thread overview]
Message-ID: <20090124142331.GA32688@infradead.org> (raw)
In-Reply-To: <497926DC.1030509@sgi.com>
On Fri, Jan 23, 2009 at 01:09:32PM +1100, Mark Goodwin wrote:
>
> A known limitation of xfs_repair is the large amount of memory it
> requires, depending on filesystem size and number of inodes, etc.
>
> The attached patch series, originally by Barry Bnaujok, is close to
> being finished but requires a new owner to do some final testing and
> polishing. It applies cleanly against top-of-tree xfsprogs-3.0.0
I did a quick look over it on the plane today and it looks quite nice
to me.
I guess there are no patch descriptions left anywhere?
Otherwise some of the patch might need some minor polishing, e.g.
the patch moving over from the radix tree to the btree leaves the
radix-tree implementation in, which gets removed in the next patch
which has otherwise unrelated changes.
The btree implementation btw worries me a little, I wonder if we need
a test harness to make sure it's correct for all corner cases.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-24 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 2:09 [PATCH, needs new owner] xfs_repair memory optimization Mark Goodwin
2009-01-24 14:23 ` Christoph Hellwig [this message]
2009-01-25 0:03 ` 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=20090124142331.GA32688@infradead.org \
--to=hch@infradead.org \
--cc=markgw@sgi.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