From: Shaohua Li <shli@kernel.org>
To: Francisco Parada <advanceandconquer@gmail.com>
Cc: "Michael J. Shaver" <jmshaver@gmail.com>,
mdraid <linux-raid@vger.kernel.org>
Subject: Re: RAID6 - CPU At 100% Usage After Reassembly
Date: Tue, 13 Sep 2016 10:43:52 -0700 [thread overview]
Message-ID: <20160913174352.GA43576@kernel.org> (raw)
In-Reply-To: <CAOW94utnY1zCR7gUCx1K0p2YfDhi3tXTsE6J_mT6rNz1TuTZEQ@mail.gmail.com>
On Tue, Sep 13, 2016 at 11:22:17AM -0400, Francisco Parada wrote:
> Hi all,
>
> I've tried the suggestions mentioned and also tried booting into an
> older version of Ubuntu (14.04.5 instead of my current 16.04.1), which
> has an older kernel per a private suggestion, but that too was
> unsuccessful. Just wanted to give a quick update that all of the
> mentioned workarounds were unfruitful.
If you could rebuild kernel and apply this debug patch, I'd like to check what
happens. When the cpu is in 100% usage and reshape stalls, please capture the
/sys/kernel/debug/tracing/trace output and send to me.
Thanks,
Shaohua
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 5883ef0..db484ca 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -62,6 +62,9 @@
#include "raid0.h"
#include "bitmap.h"
+#undef pr_debug
+#define pr_debug trace_printk
+
#define cpu_to_group(cpu) cpu_to_node(cpu)
#define ANY_GROUP NUMA_NO_NODE
next prev parent reply other threads:[~2016-09-13 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 4:04 RAID6 - CPU At 100% Usage After Reassembly Francisco Parada
2016-09-04 14:38 ` Michael J. Shaver
[not found] ` <CAOW94uv4zSGs+6be3zhcQaGZdiAgg-s4ZHZ=mszcURo6pqJyqA@mail.gmail.com>
2016-09-04 22:48 ` Francisco Parada
2016-09-13 15:22 ` Francisco Parada
2016-09-13 17:43 ` Shaohua Li [this message]
2016-09-13 18:15 ` Francisco Parada
[not found] ` <CAOW94utVBcLz191ifzKkjn+nsSthPWDAQF8R-PabcS2uPareag@mail.gmail.com>
2016-09-26 14:29 ` Francisco Parada
2016-09-30 13:06 ` Francisco Parada
2016-10-05 11:12 ` Francisco Parada
2016-10-06 23:55 ` Shaohua Li
2016-10-07 11:23 ` Francisco Parada
2016-10-10 19:52 ` Anthony Youngman
2016-10-11 3:53 ` Brad Campbell
2016-10-11 9:23 ` Wols Lists
2016-10-11 12:46 ` Brad Campbell
-- strict thread matches above, loose matches on Subject: below --
2016-09-04 2:56 Francisco Parada
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=20160913174352.GA43576@kernel.org \
--to=shli@kernel.org \
--cc=advanceandconquer@gmail.com \
--cc=jmshaver@gmail.com \
--cc=linux-raid@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 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.