From: Christoph Lameter <cl@linux.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [LSF/MM ATTEND] Expanding OS noise suppression
Date: Mon, 1 Dec 2014 10:45:21 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.11.1412011044450.2648@gentwo.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1411241345250.10694@gentwo.org>
Sorry the list address was not correct
On Mon, 24 Nov 2014, Christoph Lameter wrote:
> Recently a lot of work has been done in the kernel to be able to keep OS
> threads off low latency cores with the NOHZ work mainly pushed by Frederic
> Weisbecker (also also Paul McKenney modifying RCU for that purpose). With
> that approach we may now reduce the timer tick to a frequency of 1 per
> second. The result of that work is now available in Redhat 7.
>
> I have recently submitted work on the vmstat kworkers that makes the
> kworkers run on demand with a shepherd worker checking from a non low
> latency processor if there is actual work to be done on a processor in low
> latency mode. If not then the kworker requests can be avoided and
> therefore activities on that processor are reduced. This approach can be
> extended to cover other necessary activities on low latency cores.
>
> There is other work in progress to limit unbound kworker threads to no
> NOHZ processors. Also more work is in flight to work on various issues in
> the scheduler to enable us to hold off the timer tick for more than one
> second.
>
> There are numerous other issues that can impact on a low latency core from
> the memory management system. I would like to discuss ways that we can
> further ensure that OS activities do not impact latency critical threads
> running on special nohz cores.
>
> This may cover:
> - minor and major faults and how to suppress them effectively.
> - Processor cache impacts by sibling threads.
> - IPIs
> - Control over various subsystem specific per cpu threads.
> - Control impacts of scans for defragmentation and THP on these cores.
>
> There was a recent discussion on the subject matter on lkml that mentions
> a number of the pending issues in this area:
>
> https://lkml.org/lkml/2014/11/11/679
> https://lkml.org/lkml/2014/10/31/364
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-12-01 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 20:06 Christoph Lameter
2014-12-01 16:45 ` Christoph Lameter [this message]
2014-12-01 17:11 ` [Lsf-pc] " Rik van Riel
2014-12-01 18:22 ` Christoph Lameter
2014-12-03 1:31 ` Andy Lutomirski
2014-12-03 15:32 ` Christoph Lameter
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=alpine.DEB.2.11.1412011044450.2648@gentwo.org \
--to=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=paulmck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox