public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: ebiederm@xmission.com
Subject: 2.6.19-rc1: Slowdown in lmbench's fork
Date: Thu, 02 Nov 2006 08:44:57 -0800	[thread overview]
Message-ID: <1162485897.10806.72.camel@localhost.localdomain> (raw)


After introduction of the following patch:

[PATCH] genirq: x86_64 irq: make vector_irq per cpu
http://kernel.org/git/?
p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=550f2299ac8ffaba943cf211380d3a8d3fa75301

we see fork benchmark in lmbench-3.0-a7 slowed by 
11.5% on a 2 socket woodcrest machine.  Similar change
is seen also on other SMP Xeon machines.

When running lmbench, we have chosen the lmbench option
to pin parent and child on different processor cores 
  
Overhead of calling sched_setaffinity to place the process 
on processor is included in lmbench's fork time measurement. 
The patch may play a role in increasing this.

The two follow up patches to the original "make vector_irq per cpu" 
did not affect the fork time.

[PATCH] x86_64 irq: Properly update vector_irq
[PATCH] x86-64: Only look at per_cpu data for online ...

Tim

             reply	other threads:[~2006-11-02 17:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 16:44 Tim Chen [this message]
2006-11-02 18:33 ` 2.6.19-rc1: Slowdown in lmbench's fork Eric W. Biederman
2006-11-02 18:34   ` Tim Chen
2006-11-03  2:11     ` 2.6.19-rc1: x86_64 slowdown " Adrian Bunk
2006-11-03  9:08       ` Eric W. Biederman
2006-11-03 16:10       ` Tim Chen
2006-11-03 17:35         ` Eric W. Biederman
2006-11-03 17:47           ` Andi Kleen
2006-11-03 18:18             ` Eric W. Biederman
2006-11-03 18:39               ` Andi Kleen
2006-11-03 20:25             ` Tim Chen

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=1162485897.10806.72.camel@localhost.localdomain \
    --to=tim.c.chen@linux.intel.com \
    --cc=ebiederm@xmission.com \
    --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