From: Pavel Goran <via-bcache@pvgoran.name>
To: linux-bcache@vger.kernel.org
Subject: Re[2]: 3.17: bcache_gc: BUG: soft lockup - CPU#2 stuck for 22s!
Date: Fri, 31 Oct 2014 16:35:13 +0600 [thread overview]
Message-ID: <94854461.20141031163513@pvgoran.name> (raw)
In-Reply-To: <CAC8teKWQLjE8HgGg5mBG14oSHyCeK_vosnt+wXoiGEG8-svUCg@mail.gmail.com>
Hello Zhu,
Friday, October 31, 2014, 3:20:32 PM, you wrote:
> Theoretically this livelock does exist all the way, however we can't
> reproduce it on 3.17 kernel, or maybe it's just because the stress is
> not big enough. Anyway it can be reproduced easily on RHEL6 kernel (we
> have ported bcache back to the RHEL6 kernel). Dunno if it's caused by
> the differences between the schedulers.
My experience shows that scheduler can be a factor here. I regularly had the
lockup issue while running a kernel with BFS scheduler (pf-kernel). Then I
switched to CFS and lockups disappeared. (Now I'm running 3.17 with BFS and
with the October 18 patch from the mailing list, no issues as of yet.)
Pavel Goran
next prev parent reply other threads:[~2014-10-31 10:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 0:25 3.17-rc6: bcache_gc: BUG: soft lockup - CPU#2 stuck for 23s! Eric Wheeler
2014-10-27 2:52 ` 3.17: bcache_gc: BUG: soft lockup - CPU#2 stuck for 22s! Eric Wheeler
2014-10-31 9:20 ` Zhu Yanhai
2014-10-31 10:35 ` Pavel Goran [this message]
2014-11-01 2:35 ` Eric Wheeler
2014-11-01 20:44 ` 3.17-rc6: bcache_gc: BUG: soft lockup - CPU#2 stuck for 23s! Kent Overstreet
2014-11-21 22:54 ` Stefan Seyfried
2014-11-21 23:20 ` Kent Overstreet
2014-11-22 0:22 ` Eric Wheeler
2014-11-22 12:46 ` Stefan Seyfried
2014-11-24 18:52 ` Eric Wheeler
2014-12-03 9:32 ` Stefan Seyfried
2014-12-03 11:25 ` Thomas Stein
2014-11-23 11:17 ` Thomas Stein
2014-11-24 18:49 ` Eric Wheeler
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=94854461.20141031163513@pvgoran.name \
--to=via-bcache@pvgoran.name \
--cc=linux-bcache@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.