From: Anton Blanchard <anton@samba.org>
To: shreyas@linux.vnet.ibm.com, ego@linux.vnet.ibm.com,
mpe@ellerman.id.au, mikey@neuling.org,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: cpuidle broken on mainline
Date: Thu, 23 Jun 2016 01:16:55 +1000 [thread overview]
Message-ID: <20160623011655.62c610bd@kryten> (raw)
Hi,
I was noticing some pretty big run to run variations on single threaded
benchmarks, and I've isolated it cpuidle issues. If I look at
the cpuidle tracepoint, I notice we only go into the snooze state.
Do we have any known bugs in cpuidle at the moment?
While looking around, I also noticed PM_QOS_CPU_DMA_LATENCY,
which seems like a bad thing for us. It is used in places like
the e1000e adapter:
drivers/net/ethernet/intel/e1000e/netdev.c:
pm_qos_add_request(&adapter->pm_qos_req, PM_QOS_CPU_DMA_LATENCY
Seems like that would force us into SMT8 mode all the time. Can we
disable it on ppc64le completely?
Anton
next reply other threads:[~2016-06-22 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:16 Anton Blanchard [this message]
2016-06-22 19:39 ` cpuidle broken on mainline Shreyas B Prabhu
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=20160623011655.62c610bd@kryten \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=ego@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=shreyas@linux.vnet.ibm.com \
/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.