From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lots of brief rcu stalls.
Date: Thu, 5 Dec 2013 09:31:02 -0800 [thread overview]
Message-ID: <20131205173102.GS15492@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131205171550.GA30002@redhat.com>
On Thu, Dec 05, 2013 at 12:15:50PM -0500, Dave Jones wrote:
> On Thu, Dec 05, 2013 at 08:49:12AM -0800, Paul E. McKenney wrote:
>
> > But what workload are you running that causes this? The only way I
> > can think of to make this happen requires that you have at least one
> > CPU spending more than 21 seconds running continuously in kernel mode.
> > Is that what you are doing, or have you come up with some other creative
> > way for this to happen? In the latter case, I would really like to know
> > about it in case it exposes yet another flaw in my RCU design. ;-)
>
> just the regular trinity runs, so it could be anything.
> (Running a few instances of it, with a couple dozen child processes each to drive up the loadavg)
Well, trinity has caused kernel-mode execution periods in excess of
21 seconds in the past, so I will assume that this is the cause until
further notice.
> if only I had a trace or something that I could start to guess at what was happening :)
Maybe creating such a trace would expose additional bugs. ;-)
Thanx, Paul
next prev parent reply other threads:[~2013-12-05 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 23:28 lots of brief rcu stalls Dave Jones
2013-12-05 0:16 ` Paul E. McKenney
2013-12-05 1:22 ` Dave Jones
2013-12-05 2:44 ` Paul E. McKenney
2013-12-05 16:49 ` Paul E. McKenney
2013-12-05 17:15 ` Dave Jones
2013-12-05 17:31 ` Paul E. McKenney [this message]
2013-12-05 2:18 ` Eric Dumazet
2013-12-05 2:36 ` Joe Perches
2013-12-05 2:51 ` Paul E. McKenney
2013-12-05 2:43 ` Paul E. McKenney
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=20131205173102.GS15492@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=davej@redhat.com \
--cc=linux-kernel@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