From: Chris Mason <chris.mason@oracle.com>
To: yanhai zhu <zhu.yanhai@gmail.com>
Cc: Liu Hui <onlyflyer@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATH]Some fix for batching extent insert.
Date: Tue, 18 Nov 2008 09:48:58 -0500 [thread overview]
Message-ID: <1227019738.15917.5.camel@think.oraclecorp.com> (raw)
In-Reply-To: <977a2be20811180635u21f4dbbakd9dbc3a6665960d2@mail.gmail.com>
On Tue, 2008-11-18 at 22:35 +0800, yanhai zhu wrote:
> hello,
> In fact, Before Liu's change, this function maybe don't wait and
> insert ALL extents when all=1 in some cases,
> please think about the following conditions:
>
Ok, I see what you mean. It turned out it was actually the other hunk
that was breaking things. I think Liu is right about that bug as well,
but I changed it slightly to preserve the counter updating but avoid
touching the list if we're really done.
Thanks!
-chris
prev parent reply other threads:[~2008-11-18 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 15:48 [PATH]Some fix for batching extent insert Liu Hui
2008-11-18 12:17 ` Chris Mason
2008-11-18 12:30 ` Chris Mason
2008-11-18 14:35 ` yanhai zhu
2008-11-18 14:48 ` Chris Mason [this message]
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=1227019738.15917.5.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=onlyflyer@gmail.com \
--cc=zhu.yanhai@gmail.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