All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] Ocfs2: Make ocfs2_find_cpos_for_left_leaf() public.
Date: Wed, 5 May 2010 18:54:31 -0700	[thread overview]
Message-ID: <20100506015430.GD9955@mail.oracle.com> (raw)
In-Reply-To: <4BE22060.7040405@oracle.com>

On Thu, May 06, 2010 at 09:50:24AM +0800, tristan wrote:
> Joel Becker wrote:
> > On Mon, Apr 12, 2010 at 04:11:26PM +0800, Tristan Ye wrote:
> >   
> >> The original idea to pull ocfs2_find_cpos_for_left_leaf() out of
> >> alloc.c is to benefit punching-holes optimization patch, it however,
> >> can also be referred by other funcs in the future who want to do the
> >> same job.
> >>
> >> Signed-off-by: Tristan Ye <tristan.ye@oracle.com>
> >>     
> >
> > Tristan,
> > 	Don't these patches sit atop another truncate cleanup?  Can you
> > send me an entire series with everything required for cleanup and
> > optimization of truncate and hole clearing.

	If you're rebasing, do it atop merge-window, which is the
already-queued stuff for 2.6.35.

Joel

-- 

"The whole principle is wrong; it's like demanding that grown men 
 live on skim milk because the baby can't eat steak."
        - author Robert A. Heinlein on censorship

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2010-05-06  1:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12  8:11 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Make ocfs2_find_cpos_for_left_leaf() public Tristan Ye
2010-04-12  8:11 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Optimize punching-hole codes v5 Tristan Ye
2010-05-06  1:11 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Make ocfs2_find_cpos_for_left_leaf() public Joel Becker
2010-05-06  1:50   ` tristan
2010-05-06  1:54     ` Joel Becker [this message]
2010-05-06  2:10       ` tristan
  -- strict thread matches above, loose matches on Subject: below --
2010-04-09  8:44 Tristan Ye

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=20100506015430.GD9955@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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.