linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Rik van Riel <riel@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Expanding OS noise suppression
Date: Mon, 1 Dec 2014 12:22:20 -0600 (CST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1412011215240.2903@gentwo.org> (raw)
In-Reply-To: <547CA12A.6010102@redhat.com>

On Mon, 1 Dec 2014, Rik van Riel wrote:

> This is a very interesting topic, but I am not sure the right audience
> for many of these discussions will be at LSF/MM...

Well some of it at least is relevant.

> Besides the minor and major faults, and the THP related defragmentation,
> which of the problems could actually be addressed by the memory
> management subsystem?

One of the motivations for the development of SLUB for example was the
long periods of latency generated by SLAB's object expiration. There are
numerous code segment in the mm subsystem that can cause suprisingly long
latencies for the application. Memory allocations through the page
allocator are on of the most severe examples.

The SLUB allocator's per cpu partial pages introduce some new latencies
(not as bad as SLAB but still) and I have seen that RT people compile that
cpu partial page support out because it causes higher variability.

Some way for the application to know and be able to avoid these would be
great.

> Would you have a list of other items in the memory management subsystem
> that cause latency issues?

I mentioned some above. There are numeous issues arising from various
pieces of heavy operations of the mm subsystems which involve page
migration, writeback, general page table walks, statistics keeping etc
etc.

> Is the minor & major fault thing an actual problem for people with real
> time applications?

Yes. The timeframes for electronic trading are lower than the time it
takes for a fault to be processed. A fault occurring at the wrong time
causes an immediate hit on the bottom line.

> Do you have any ideas on how we could solve the defragmentation and THP
> issue? Even strawman proposals to start a discussion could be useful...

Right now we disable automatic defrag and do a run of defrag and THP
before the start of business manually. There are cores that are dedicated
for the OS where the defrag etc can run during business hours and which
could also do these jobs remotely for the low latency cores if one is
careful and does not create too many latency issues on the remote cores.

--
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>

  reply	other threads:[~2014-12-01 18:22 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
2014-12-01 17:11   ` [Lsf-pc] " Rik van Riel
2014-12-01 18:22     ` Christoph Lameter [this message]
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.1412011215240.2903@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 \
    --cc=riel@redhat.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