public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Christoph Lameter <clameter@sgi.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] SLUB use cmpxchg_local
Date: Tue, 04 Sep 2007 20:02:42 +0000	[thread overview]
Message-ID: <20070904200242.GB8157@Krystal> (raw)
In-Reply-To: <Pine.LNX.4.64.0708271811200.10344@schroedinger.engr.sgi.com>

* Christoph Lameter (clameter@sgi.com) wrote:
> Measurements on IA64 slub w/per cpu vs slub w/per cpu/cmpxchg_local 
> emulation. Results are not good:
> 

Hi Christoph,

I tried to come up with a patch set implementing the basics of a new
critical section: local_enter(flags) and local_exit(flags).

Can you try those on ia64 and tell me if the results are better ?

See the 2 next posts...

Mathieu
-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  parent reply	other threads:[~2007-09-04 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1188197539.6114.426.camel@twins>
     [not found] ` <Pine.LNX.4.64.0708271237580.5056@schroedinger.engr.sgi.com>
     [not found]   ` <20070827202203.GB5653@Krystal>
     [not found]     ` <Pine.LNX.4.64.0708271324001.5884@schroedinger.engr.sgi.com>
     [not found]       ` <20070827203913.GA7416@Krystal>
     [not found]         ` <Pine.LNX.4.64.0708271401070.6435@schroedinger.engr.sgi.com>
     [not found]           ` <20070827211003.GA10627@Krystal>
     [not found]             ` <Pine.LNX.4.64.0708271421130.6566@schroedinger.engr.sgi.com>
     [not found]               ` <20070827213845.GB9748@Krystal>
     [not found]                 ` <Pine.LNX.4.64.0708271510020.8783@schroedinger.engr.sgi.com>
     [not found]                   ` <20070827222715.GA16982@Krystal>
2007-08-28  1:26                     ` [PATCH] SLUB use cmpxchg_local Christoph Lameter
2007-08-28 12:07                       ` Mathieu Desnoyers
2007-08-28 19:42                         ` Christoph Lameter
2007-09-04 20:02                       ` Mathieu Desnoyers [this message]
2007-09-04 20:03                       ` [PATCH] local_t protection (critical section) Mathieu Desnoyers
2007-09-04 20:04                       ` [PATCH] slub - Use local_t protection Mathieu Desnoyers
2007-09-04 20:45                         ` Christoph Lameter
2007-09-05 13:03                           ` Mathieu Desnoyers
2007-09-05 13:04                           ` [PATCH] local_t protection (critical section) Mathieu Desnoyers
2007-09-12 22:33                             ` Christoph Lameter
2007-09-12 23:00                               ` Mathieu Desnoyers
2007-09-05 13:06                           ` [PATCH] slub - Use local_t protection Mathieu Desnoyers
2007-09-12 22:28                             ` 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=20070904200242.GB8157@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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