From: "Yan, Zheng" <zheng.yan@oracle.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 02/12] Btrfs: Kill allocate_wait in space_info
Date: Mon, 19 Apr 2010 22:46:12 +0800 [thread overview]
Message-ID: <s2o3d0408631004190746wcc55e7bdp572e9cce8a36fcd6@mail.gmail.com> (raw)
In-Reply-To: <20100419135713.GA2352@localhost.localdomain>
On Mon, Apr 19, 2010 at 9:57 PM, Josef Bacik <josef@redhat.com> wrote:
> The purpose of maybe_allocate_chunk was that there is no way to know =
if some
> other CPU is currently trying to allocate a chunk for the given space=
info. =A0We
> could have two cpu's come inot do_chunk_alloc at relatively the same =
time and
> end up allocating twice the amount of space, which is why I did the w=
aitqueue
> thing. =A0It seems like this is still a possibility with your patch. =
=A0Thanks,
>
This is impossible because the very first thing do_chunk_alloc does is
lock the chunk_mutex.
Yan, Zheng
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-19 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 10:45 [PATCH 02/12] Btrfs: Kill allocate_wait in space_info Yan, Zheng
2010-04-19 13:57 ` Josef Bacik
2010-04-19 14:46 ` Yan, Zheng [this message]
2010-04-19 14:48 ` Josef Bacik
2010-04-19 15:34 ` Yan, Zheng
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=s2o3d0408631004190746wcc55e7bdp572e9cce8a36fcd6@mail.gmail.com \
--to=zheng.yan@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).