public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] libxfs: reintroduce old xfs_repair radix-tree code
Date: Wed, 09 Feb 2011 12:05:13 -0600	[thread overview]
Message-ID: <1297274713.2513.27.camel@doink> (raw)
In-Reply-To: <1294649091-27174-2-git-send-email-david@fromorbit.com>

On Mon, 2011-01-10 at 19:44 +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
> 
> The current kernel code uses radix trees more widely than the
> previous code, so for the next sync we need radix tree support in
> libxfs. Pull the old radix tree code out the xfs_repair git history
> and move it into libxfs to simplify the kernel code sync.
> 
> Signed-off-by: Dave Chinner <dchinner@redhat.com>

OK, I actually reviewed this code, even though it had
already been present in the source tree prior to commit:
379397bf9... ("repair: use a btree instead of a radix tree
for the prefetch queue").

And I have some suggestions, and I have at least one
thing that I think is a bug.

I also notice that this code apparently formed the
basis of the kernel's implementation.  That's good.
It's probably worth reviewing the kernel version's
history to see if there are any bug fixes that ought
to be brought back into this code (and vice-versa).


All that being said, I think the right thing to do
is to include this change as-is as a commit.  It
includes both "radix-tree.c" and "radix-tree.h" as
identical copies of what was removed (though each
now resides in a different directory from before),
thereby preserving the provenance of the code.

Then, after it's committed, I can offer my suggested
changes, or even just implement and propose them
myself.

So unless you disagree with this approach I think
it's fine to commit it as you originally posted it.

Reviewed-by: Alex Elder <aelder@sgi.com>



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

  parent reply	other threads:[~2011-02-09 18:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10  8:44 [PATCH 0/3] xfsprogs: sync up with 2.6.38 kernel code V2 Dave Chinner
2011-01-10  8:44 ` [PATCH 1/3] libxfs: reintroduce old xfs_repair radix-tree code Dave Chinner
2011-01-24  8:58   ` Christoph Hellwig
2011-02-09 18:05   ` Alex Elder [this message]
2011-02-14  0:36     ` Dave Chinner
2011-01-10  8:44 ` [PATCH 2/3] libxlog: sync up with 2.6.38 kernel code Dave Chinner
2011-01-24  8:47   ` Christoph Hellwig
2011-01-24 23:47     ` Dave Chinner
2011-02-09 21:49   ` Alex Elder
2011-02-14  5:10     ` Dave Chinner
2011-02-14  5:31       ` Dave Chinner
2011-02-14  5:46       ` Dave Chinner
2011-01-10  8:44 ` [PATCH 3/3] libxfs: sync files " Dave Chinner
2011-01-24  8:57   ` Christoph Hellwig
2011-01-24 23:55     ` Dave Chinner
2011-02-10 19:02   ` Alex Elder
2011-02-14  6:30 ` [PATCH 0/3] xfsprogs: sync up with 2.6.38 kernel code V2 Dave Chinner
2011-02-22 20:45   ` Alex Elder
2011-03-07 18:14   ` Alex Elder
2011-03-07 18:24     ` Christoph Hellwig
2011-04-13 16:34   ` Alex Elder

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=1297274713.2513.27.camel@doink \
    --to=aelder@sgi.com \
    --cc=david@fromorbit.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