From: Andrew Morton <akpm@zip.com.au>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] low-latency zap_page_range()
Date: Thu, 29 Aug 2002 13:59:17 -0700 [thread overview]
Message-ID: <3D6E8B25.425263D5@zip.com.au> (raw)
In-Reply-To: 1030653602.939.2677.camel@phantasy
Robert Love wrote:
>
> ...
> unless we
> wanted to unconditionally drop the locks and let preempt just do the
> right thing and also reduce SMP lock contention in the SMP case.
That's an interesting point. page_table_lock is one of those locks
which is occasionally held for ages, and frequently held for a short
time.
I suspect that yes, voluntarily popping the lock during the long holdtimes
will allow other CPUs to get on with stuff, and will provide efficiency
increases. (It's a pretty lame way of doing that though).
But I don't recall seeing nasty page_table_lock spintimes on
anyone's lockmeter reports, so...
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@zip.com.au>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] low-latency zap_page_range()
Date: Thu, 29 Aug 2002 13:59:17 -0700 [thread overview]
Message-ID: <3D6E8B25.425263D5@zip.com.au> (raw)
In-Reply-To: 1030653602.939.2677.camel@phantasy
Robert Love wrote:
>
> ...
> unless we
> wanted to unconditionally drop the locks and let preempt just do the
> right thing and also reduce SMP lock contention in the SMP case.
That's an interesting point. page_table_lock is one of those locks
which is occasionally held for ages, and frequently held for a short
time.
I suspect that yes, voluntarily popping the lock during the long holdtimes
will allow other CPUs to get on with stuff, and will provide efficiency
increases. (It's a pretty lame way of doing that though).
But I don't recall seeing nasty page_table_lock spintimes on
anyone's lockmeter reports, so...
--
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/
next prev parent reply other threads:[~2002-08-29 20:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 15:31 [PATCH] low-latency zap_page_range() Robert Love
2002-08-29 15:31 ` Robert Love
2002-08-29 20:30 ` Andrew Morton
2002-08-29 20:30 ` Andrew Morton
2002-08-29 20:40 ` Robert Love
2002-08-29 20:40 ` Robert Love
2002-08-29 20:46 ` Robert Love
2002-08-29 20:46 ` Robert Love
2002-08-29 20:59 ` Andrew Morton [this message]
2002-08-29 20:59 ` Andrew Morton
2002-08-29 21:38 ` William Lee Irwin III
2002-08-29 21:38 ` William Lee Irwin III
2002-08-29 22:37 ` Linus Torvalds
2002-08-29 23:06 ` William Lee Irwin III
2002-08-29 21:00 ` Andrew Morton
2002-08-29 21:00 ` Andrew Morton
2002-08-29 21:12 ` Robert Love
2002-08-29 21:12 ` Robert Love
2002-08-29 21:22 ` Andrew Morton
2002-08-29 21:22 ` Andrew Morton
2002-08-29 21:46 ` Rik van Riel
2002-08-29 21:46 ` Rik van Riel
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=3D6E8B25.425263D5@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rml@tech9.net \
/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.