From: Andi Kleen <ak@muc.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Page Fault Scalability patch V19 [4/4]: Drop use of page_table_lock in do_anonymous_page
Date: 10 Mar 2005 00:21:41 +0100
Date: Thu, 10 Mar 2005 00:21:41 +0100 [thread overview]
Message-ID: <20050309232141.GD63395@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0503091515440.30604@schroedinger.engr.sgi.com>
On Wed, Mar 09, 2005 at 03:17:10PM -0800, Christoph Lameter wrote:
> On Wed, 10 Mar 2005, Andi Kleen wrote:
>
> > > If atomic64_t is available on all 64 bit systems then its no problem.
> >
> > Most of them have it already. parisc64/ppc64/sh64 are missing it,
> > but I assume they will catch up quickly.
>
> Changing the type for the countedrs is possible by only changing the
> definition of MM_COUNTER_T in include/sched.h. I would prefer to wait
> until atomic64_t is available on all 64 bit platforms before making that
> part of this patch.
Well, they will not move until someone uses it (especially parisc
and sh64 which always are quite out of sync in mainline). ppc64
usually moves quickly.
But adding arbitary limits like this even temporarily is imho
a bad idea.
-Andi
next prev parent reply other threads:[~2005-03-09 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 20:13 Page Fault Scalabilty patch V19 [0/4]: Overview Christoph Lameter
2005-03-09 20:13 ` Page Fault Scalability patch V19 [1/4]: pte_cmpxchg and CONFIG_ATOMIC_TABLE_OPS Christoph Lameter
2005-03-09 23:01 ` Andi Kleen
2005-03-09 23:06 ` Christoph Lameter
2005-03-09 20:13 ` Page Fault Scalability patch V19 [2/4]: Abstract mm_struct counter operations Christoph Lameter
2005-03-09 20:13 ` Page Fault Scalability patch V19 [3/4]: Drop use of page_table_lock in handle_mm_fault Christoph Lameter
2005-03-09 20:13 ` Page Fault Scalability patch V19 [4/4]: Drop use of page_table_lock in do_anonymous_page Christoph Lameter
2005-03-09 22:56 ` Andi Kleen
2005-03-09 23:02 ` Christoph Lameter
2005-03-09 23:14 ` Andi Kleen
2005-03-09 23:17 ` Christoph Lameter
2005-03-09 23:21 ` Andi Kleen [this message]
2005-03-09 23: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=20050309232141.GD63395@muc.de \
--to=ak@muc.de \
--cc=clameter@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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