mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: nickpiggin@yahoo.com.au, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: big bw_pipe drop due to sched-domain patch?
Date: Fri, 28 May 2004 21:59:14 -0700	[thread overview]
Message-ID: <16568.6306.306924.154136@napali.hpl.hp.com> (raw)

Today I noticed that going from 2.6.6 to 2.6.7-rc1 caused a big drop
in LMbench2 bw_pipe throughput on a dual-CPU machine (2.6.7-rc1 shows
10 times lower bandwidth than 2.6.6).  It appears that the drop is due
to the two tasks being distributed across the two CPUs, rather than
being kept on the same CPU.  If I force the tasks to be pinned on a
single CPU, e.g., like so:

	$ taskset 1 ./bw_pipe

then performance is "only" about 10% worse than with 2.6.6.

Is this kind of drop expected?

	--david

             reply	other threads:[~2004-05-29  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29  4:59 David Mosberger [this message]
2004-05-29  5:18 ` Nick Piggin

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=16568.6306.306924.154136@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=akpm@osdl.org \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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
all inboxes | Powered by JetHome®