From: Dipankar Sarma <dipankar@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Anton Blanchard <anton@au1.ibm.com>
Subject: Re: [patch] smptimers, old BH removal, tq-cleanup, 2.5.39
Date: Thu, 3 Oct 2002 12:40:17 +0530 [thread overview]
Message-ID: <20021003124017.B15070@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210010542240.2564-100000@localhost.localdomain>; from mingo@elte.hu on Tue, Oct 01, 2002 at 05:51:45AM +0200
On Tue, Oct 01, 2002 at 05:51:45AM +0200, Ingo Molnar wrote:
>
> the smp_processor_id()/(HZ*num_cpus) 'interleaving' of every APIC clock
> was an SMP scalability issue, and it was done as part of the smptimers
> patch. It just got into the kernel much earlier.
>
> but these days, with the removal of BHs, it might be less of a factor,
> mainly because timers have no global synchronization anymore, so we can
> again try to not interleave the APIC clocks. Only testing will tell,
> because there might be some interaction between timer-generated code
> still.
>
> Dipankar, wli, would it be possible to try the attached simple patch with
> some of the more complex networking loads? The patch gets rid of the APIC
> timer interleaving.
>
Ingo,
Removal of interleaving of apic timers doesn't seem to have any adverse affect.
Here are some numbers from a 16-CPU NUMA-Q with tbench (32 clients) averaged
over 5 runs -
2.5.40-vanilla - 44.16 MB/Sec
2.5.40-no-clock-interleave - 44.17 MB/Sec
Thanks
--
Dipankar Sarma <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.
next prev parent reply other threads:[~2002-10-03 6:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 17:52 [patch] smptimers, old BH removal, tq-cleanup, 2.5.39 Ingo Molnar
2002-09-29 18:38 ` Jeff Garzik
2002-09-29 18:50 ` Jeff Garzik
2002-09-29 19:27 ` Ingo Molnar
2002-09-29 19:48 ` Jeff Garzik
2002-09-29 18:54 ` Dave Jones
2002-09-29 19:15 ` Dipankar Sarma
2002-09-30 0:20 ` David S. Miller
2002-09-30 4:33 ` Dipankar Sarma
2002-09-30 4:28 ` David S. Miller
2002-09-30 4:38 ` Arnaldo Carvalho de Melo
2002-09-30 12:55 ` Alan Cox
2002-09-30 14:50 ` Arnaldo Carvalho de Melo
2002-09-29 19:16 ` Ingo Molnar
2002-09-30 0:39 ` David S. Miller
2002-09-30 6:06 ` Ingo Molnar
2002-09-30 21:45 ` george anzinger
2002-10-01 3:51 ` Ingo Molnar
2002-10-01 4:18 ` David S. Miller
2002-10-01 5:24 ` Ingo Molnar
2002-10-01 8:00 ` george anzinger
2002-10-01 5:33 ` Dipankar Sarma
2002-10-03 7:10 ` Dipankar Sarma [this message]
2002-09-30 23:37 ` Christoph Hellwig
2002-09-30 16:38 ` Ingo Molnar
2002-09-30 23:45 ` Christoph Hellwig
2002-09-30 17:12 ` Ingo Molnar
2002-10-01 0:43 ` Christoph Hellwig
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=20021003124017.B15070@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=anton@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.