From: "Stephen C. Tweedie" <sct@redhat.com>
To: Hai Huang <haih@eecs.umich.edu>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: active_mm and mm
Date: Tue, 20 Aug 2002 16:52:35 +0100 [thread overview]
Message-ID: <20020820165235.I2645@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0208201031570.18993-100000@wildwood.eecs.umich.edu>; from haih@eecs.umich.edu on Tue, Aug 20, 2002 at 10:55:04AM -0400
Hi,
On Tue, Aug 20, 2002 at 10:55:04AM -0400, Hai Huang wrote:
> Ok, I see why we're differentiating between mm and active_mm, but is this
> actually giving us a lot of benefits considering the number of context switches
> that would actually take advantage of this feature is probably small
> (well, it depends on the workload).
It's actually enormous. There are a lot of kernel daemons that do
background IO, for example. Those are often waking up after an IO
completes, doing a tiny amount of work to submit new IO, then sleeping
again. Even more significant in many workloads is the idle task.
> Also, is the tlb flush operation that
> expensive?
Yes. Modern cpus are _way_ faster than main memory, and they rely
utterly on the cache architecture to keep them busy. Doing a tlb
flush forces the CPU to go back to main memory up to 2 times for every
single address translation that follows until the tlb is full again.
That's an enormous cost, especially on rapidly-switching workloads.
--Stephen
--
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/
prev parent reply other threads:[~2002-08-20 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 2:09 Hai Huang
2002-08-20 9:19 ` Stephen C. Tweedie
2002-08-20 14:55 ` Hai Huang
2002-08-20 15:52 ` Stephen C. Tweedie [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=20020820165235.I2645@redhat.com \
--to=sct@redhat.com \
--cc=haih@eecs.umich.edu \
--cc=linux-mm@kvack.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