From: Nivedita Singhvi <niv@us.ibm.com>
To: J_Fraser@bit-net.com
Cc: "'Robert Olsson'" <Robert.Olsson@data.slu.se>, netdev@oss.sgi.com
Subject: Re: [Question] SMP for Linux
Date: Fri, 18 Oct 2002 17:20:06 -0700 [thread overview]
Message-ID: <3DB0A536.A8FB364A@us.ibm.com> (raw)
In-Reply-To: 000b01c276fe$46626720$3701020a@CONCORDIA
Jon Fraser wrote:
> bound = interrupts for both cards bound to one cpu
> float = no smp affinity
> split = card 0 bound to cpu 0, card 1 bound to cpu 1
>
> The results, in kpps:
>
> bound float split
> cpu % cpu% cpu%
> -----------------------
> 1 flow 290 270 290
> 99%x1 65%x2 99%x1
>
> 2 flows 270 380 450
> 99%x1 82%x2 96%x2
This is approximately what one should expect, correct? If
you have only one task (flow), then the float case will be
slower than the bound/split case (as long as the CPU isnt the
bottleneck), because you'll have an increasing number of
cacheline misses. When you have two or more flows, the
general order in which things improve would be the bound,
float and then split cases. The fact that the float case is
halfway between the other two is indicative of how expensive
the cacheline being on the other CPU is.
In the float case, it would be nice if we could see the interrupt
distribution between the CPU's. Would you happen to have the
/proc/interrupt info?
thanks,
Nivedita
next prev parent reply other threads:[~2002-10-19 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 2:29 [Question] SMP for Linux Hyochang Nam
2002-10-17 10:02 ` bert hubert
2002-10-17 12:00 ` Robert Olsson
2002-10-17 17:28 ` Jon Fraser
2002-10-18 16:16 ` Robert Olsson
2002-10-18 23:29 ` Jon Fraser
2002-10-19 0:20 ` Nivedita Singhvi [this message]
2002-10-19 7:53 ` Robert Olsson
2002-10-24 21:00 ` Jon Fraser
2002-11-13 6:53 ` Eric Lemoine
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=3DB0A536.A8FB364A@us.ibm.com \
--to=niv@us.ibm.com \
--cc=J_Fraser@bit-net.com \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).