public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "Christoph Lameter" <clameter@sgi.com>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Call percpu smp cacheline algin interface
Date: Wed, 9 May 2007 16:36:16 -0700	[thread overview]
Message-ID: <20070509163616.e8a36a4c.akpm@linux-foundation.org> (raw)
In-Reply-To: <A29F7A5700A7EA4380E08C1F68C3B6D802B5F7CA@scsmsx411.amr.corp.intel.com>

On Wed, 9 May 2007 16:10:05 -0700
"Yu, Fenghua" <fenghua.yu@intel.com> wrote:

> 
> 
> On Wed, 9 May 2007, Andrew Morton wrote:
> 
> >> erm, it's not obviosu from all this that the patches are worth
> proceeding
> >> with, are they?
> 
> >What was it? 0.5% performance improvement on a synthetic benchmark? 
> >Process wakeup I believe?
> 
> The initial patch and discussion is from:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0704.1/0340.html
> 
> Yes, the runqueue patch has a 0.5% perf improvement on database
> workload(which is a good improvement for this workload).
> 
> The theory behind the patches is:
> 
> 1. Minimize number of cache lines that are touched during a remote
> access. On Numa system, remote access is more expensive than local.
> 2. Do not share cache line between remote accessed data and local
> accessed data. Local data update may cause remote access cache miss and
> wait for longer time.
> 
> Although the patches themselves don't save or waste per_cpu size, the
> above two reasons are good to have them in.
> 

Guys, this is all a lesson in the value of changelogs, and in how not to
write them.

Can you please prepare a new changelog for these patches?  Something which
encapsulates all the above in as brief a form as possible and which
includes some numbers describing the space and/or speed improvements?

Thanks.

      reply	other threads:[~2007-05-09 23:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <33E1C72C74DBE747B7B59C1740F7443701A2F0AB@orsmsx417.amr.corp.intel.com>
2007-05-05  0:12 ` [PATCH 1/2] Define percpu smp cacheline align interface Fenghua Yu
2007-05-07 22:58   ` Fenghua Yu
2007-05-15 23:42     ` Andrew Morton
2007-05-05  0:12 ` [PATCH 0/2] Add percpu smp cacheline align section Fenghua Yu
2007-05-05 16:52   ` Christoph Lameter
2007-05-07 17:11     ` Siddha, Suresh B
2007-05-07 17:30       ` Christoph Lameter
2007-05-07 17:46         ` Siddha, Suresh B
2007-05-07 18:13           ` Yu, Fenghua
2007-05-15  0:12           ` [PATCH 2/2] Use the new percpu interface for shared data -- version 2 Fenghua Yu
     [not found]           ` <20070515001255.GA27978@linux-os.sc.intel.com>
2007-05-15  0:22             ` [PATCH 1/2] Define " Fenghua Yu
2007-05-05  0:12 ` [PATCH 2/2] Call percpu smp cacheline algin interface Fenghua Yu
2007-05-07 22:59   ` Fenghua Yu
2007-05-09 20:33     ` Andrew Morton
2007-05-09 22:16       ` Yu, Fenghua
2007-05-09 22:53         ` Andrew Morton
2007-05-09 22:56           ` Christoph Lameter
2007-05-09 23:06             ` Siddha, Suresh B
2007-05-09 23:10             ` Yu, Fenghua
2007-05-09 23:36               ` Andrew Morton [this message]

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=20070509163616.e8a36a4c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suresh.b.siddha@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox