From: Chris Mason <clm@fb.com>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: <linux-btrfs@vger.kernel.org>, <jbacik@fb.com>, <chandan@mykolab.com>
Subject: Re: [PATCH V2] Btrfs: find_free_extent: Do not erroneously skip LOOP_CACHING_WAIT state
Date: Mon, 2 Nov 2015 11:52:36 -0500 [thread overview]
Message-ID: <20151102165236.GA9975@ret.masoncoding.com> (raw)
In-Reply-To: <1446452986-6581-1-git-send-email-chandan@linux.vnet.ibm.com>
On Mon, Nov 02, 2015 at 01:59:46PM +0530, Chandan Rajendra wrote:
> When executing generic/001 in a loop on a ppc64 machine (with both sectorsize
> and nodesize set to 64k), the following call trace is observed,
Thanks Chandan, I hit this same trace on x86-64 with 16K nodes.
-chris
next prev parent reply other threads:[~2015-11-02 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 19:11 [PATCH] Btrfs: find_free_extent: Do not erroneously skip LOOP_CACHING_WAIT state Chandan Rajendra
2015-11-02 8:29 ` [PATCH V2] " Chandan Rajendra
2015-11-02 15:46 ` Josef Bacik
2015-11-02 16:52 ` Chris Mason [this message]
[not found] ` <CAOcd+r3ku8mhfK_ZvZRL2pRSZ=Y1Q2maNF_ob+8fEA=2Etm1Lg@mail.gmail.com>
2015-12-13 10:18 ` Alex Lyakas
2015-12-14 7:59 ` Chandan Rajendra
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=20151102165236.GA9975@ret.masoncoding.com \
--to=clm@fb.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=chandan@mykolab.com \
--cc=jbacik@fb.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).