All of lore.kernel.org
 help / color / mirror / Atom feed
From: rwhron@earthlink.net
To: lse-tech@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: cpu affinity and lmbench - ac and mjc
Date: Wed, 17 Jul 2002 14:42:30 -0400	[thread overview]
Message-ID: <20020717184230.GA11256@rushmore> (raw)

LMbench shows some differences several local 
communication, local bandwidth, and context switch 
metrics between 2.4.19-pre10-ac2 and 2.4.19-pre10-mjc1.

The latency/bandwidth differences are similar to
2.4.19-pre10aa2 and 2.4.19-jam2, but bigger.  

In trying to isolate the differences in the aa/jam
series, it appeared the irqrate/irqbalance in jam2
was the differentiating factor.  

mjc1 and ac2 are similar to jam/aa. mjc1 is a patchset
to ac2.  mjc1 doesn't include irqrate/irqbalance though.

I ran ac2 with 1 cpu enabled on a quad xeon to get a
better idea of how processor affinity affects lmbench.

Analysis of mjc1, ac2, and ac2 with 1 cpu is here:

http://home.earthlink.net/~rwhron/kernel/lmbench_affinity.html

comments, suggestions welcome.

-- 
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html


                 reply	other threads:[~2002-07-17 22:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020717184230.GA11256@rushmore \
    --to=rwhron@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.