From: "Stephen C. Tweedie" <sct@redhat.com>
To: bcrl@redhat.com
Cc: Kanoj Sarcar <kanoj@google.engr.sgi.com>,
linux-mm@kvack.org, torvalds@transmeta.com
Subject: Re: [PATCH] workaround for lost dirty bits on x86 SMP
Date: Tue, 12 Sep 2000 11:24:38 +0100 [thread overview]
Message-ID: <20000912112438.C28418@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1000911210010.7937B-100000@kanga.kvack.org>; from bcrl@redhat.com on Mon, Sep 11, 2000 at 09:36:35PM -0400
Hi,
On Mon, Sep 11, 2000 at 09:36:35PM -0400, bcrl@redhat.com wrote:
> Fwiw, with the patch, running a make -j bzImage on a 4 way box does not
> seem to have made a difference.
Of course it won't, because you aren't testing the new behaviour!
Anonymous pages are always dirty, and shared mmaped pages in
MAP_PRIVATE regions are always clean. The only place where you need
to track the dirty bit dynamically is when you use shared writeable
mmaps --- can you measure a performance change there?
Cheers,
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-09-12 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-12 0:43 [PATCH] workaround for lost dirty bits on x86 SMP Ben LaHaise
2000-09-12 0:59 ` Kanoj Sarcar
2000-09-12 1:36 ` bcrl
2000-09-12 1:56 ` Rik van Riel
2000-09-12 2:34 ` Kanoj Sarcar
2000-09-12 3:39 ` Benjamin C.R. LaHaise
2000-09-12 6:13 ` Kanoj Sarcar
2000-09-12 10:24 ` Stephen C. Tweedie [this message]
2000-09-12 16:54 ` Ben LaHaise
2000-09-15 19:56 ` Linus Torvalds
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=20000912112438.C28418@redhat.com \
--to=sct@redhat.com \
--cc=bcrl@redhat.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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.