From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andi Kleen <ak@muc.de>
Cc: Christoph Lameter <clameter@sgi.com>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mel Gorman <mel@csn.ul.ie>,
linux-ia64@vger.kernel.org, Jens.Maurer@gmx.net
Subject: Re: [PATCH] add a clear_pages function to clear pages of higher order
Date: Thu, 24 Mar 2005 18:34:03 +0000 [thread overview]
Message-ID: <16963.2075.713737.485070@napali.hpl.hp.com> (raw)
In-Reply-To: <20050318192808.GB38053@muc.de>
>>>>> On Fri, 18 Mar 2005 20:28:08 +0100, Andi Kleen <ak@muc.de> said:
>> stores in general for clearing pages? I checked and Itanium has
>> always used non-temporal stores. So there will be no benefit for
>> us from this
Andi> That is weird. I would actually try to switch to temporal
Andi> stores, maybe it will improve some benchmarks.
That's definitely the case. See my earlier post on this topic:
http://www.gelato.unsw.edu.au/linux-ia64/0409/11012.html
Unfortunately, nobody reported any results for larger machines and/or
more interesting workloads, so the patch is in limbo at this time.
Clearly, if the CPU that's clearing the page is likely to use that
same page soon after, it'd be useful to use temporal stores.
--david
next prev parent reply other threads:[~2005-03-24 18:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0503101229420.13911@schroedinger.engr.sgi.com>
[not found] ` <1110490683.24355.17.camel@localhost>
[not found] ` <Pine.LNX.4.58.0503101702120.15940@schroedinger.engr.sgi.com>
[not found] ` <200503111008.12134.vda@port.imtp.ilyichevsk.odessa.ua>
2005-03-17 1:33 ` [PATCH] add a clear_pages function to clear pages of higher Christoph Lameter
2005-03-18 9:54 ` [PATCH] add a clear_pages function to clear pages of higher order Denis Vlasenko
2005-03-18 15:00 ` [PATCH] add a clear_pages function to clear pages of higher Christoph Lameter
2005-03-18 19:28 ` [PATCH] add a clear_pages function to clear pages of higher order Andi Kleen
2005-03-18 20:19 ` [PATCH] add a clear_pages function to clear pages of higher Christoph Lameter
2005-03-20 0:20 ` [PATCH] add a clear_pages function to clear pages of higher order Denis Vlasenko
2005-03-24 18:34 ` David Mosberger [this message]
2005-03-24 18:41 ` [PATCH] add a clear_pages function to clear pages of higher Christoph Lameter
2005-03-24 19:03 ` David S. Miller
2005-03-24 22:49 ` Christoph Lameter
2005-03-24 23:13 ` David S. Miller
2005-03-25 2:29 ` David S. Miller
2005-03-25 2:43 ` Christoph Lameter
2005-03-27 17:12 ` [PATCH] add a clear_pages function to clear pages of higher order Andi Kleen
2005-03-27 18:23 ` [PATCH] add a clear_pages function to clear pages of higher David S. Miller
2005-03-29 1:58 ` Christoph Lameter
2005-04-06 0:15 ` Christoph Lameter
2005-04-06 0:23 ` David Mosberger
2005-04-06 0:33 ` Christoph Lameter
2005-04-06 4:48 ` David Mosberger
2005-04-06 5:15 ` [PATCH] add a clear_pages function to clear pages of higher order Gerrit Huizenga
2005-04-06 16:03 ` Grant Grundler
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=16963.2075.713737.485070@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=Jens.Maurer@gmx.net \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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