From: Dave Chinner <david@fromorbit.com>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [regression, 3.15-rc1] vdso_gettimeofday hogs all my CPU
Date: Tue, 15 Apr 2014 18:11:59 +1000 [thread overview]
Message-ID: <20140415081158.GK15995@dastard> (raw)
In-Reply-To: <20140415075335.GE31578@dastard>
On Tue, Apr 15, 2014 at 05:53:36PM +1000, Dave Chinner wrote:
> Hi Peter,
>
> I'm guessing that x86 vdso problems are in your area of expertise,
> if not can you point me at the right person to bug?
And you can ignore it. The VM wasn't running the kernel I thought it
was - it was an old kernel from half way through last week. A
3.15-rc1 kernel, which I'm now testing, doesn't show the regression:
FSUse% Count Size Files/sec App Overhead
0 1600000 0 281779.0 9964735
0 3200000 0 280343.0 10174512
0 4800000 0 268615.2 11330160
0 6400000 0 264782.4 11072193
.....
It shows all sorts of interesting new inode cache reclaim imbalances,
but other than that the peak performance is back to normal...
Sorry for the noise.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2014-04-15 8:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 7:53 [regression, 3.15-rc1] vdso_gettimeofday hogs all my CPU Dave Chinner
2014-04-15 8:11 ` Dave Chinner [this message]
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=20140415081158.GK15995@dastard \
--to=david@fromorbit.com \
--cc=hpa@zytor.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