[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0710241001160.26202@schroedinger.engr.sgi.com>
Date: Wed, 24 Oct 2007 10:04:41 -0700 (PDT)
From: Christoph Lameter <clameter@....com>
To: Gautham R Shenoy <ego@...ibm.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Rusty Russel <rusty@...tcorp.com.au>,
Srivatsa Vaddagiri <vatsa@...ibm.com>,
Dipankar Sarma <dipankar@...ibm.com>,
Ingo Molnar <mingo@...e.hu>, Oleg Nesterov <oleg@...sign.ru>,
Paul E McKenney <paulmck@...ibm.com>,
Richard Gooch <rgooch@...f.csiro.au>,
Tigran Aivazian <tigran@...azian.fs.co.uk>,
Shoahua Li <shaohua.li@...ux.com>,
Ralf Baechle <ralf@...ux-mips.org>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Nathan Lynch <ntl@...ox.com>,
David Miller <davem@...emloft.net>, Paul Jackson <pj@....com>,
Josh Triplett <josh@...edesktop.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Akinobu Mita <akinobu.mita@...il.com>
Subject: Re: [RFC PATCH 0/5] Refcount based Cpu Hotplug. V2
On Wed, 24 Oct 2007, Gautham R Shenoy wrote:
> This is the version 2 of the refcount based cpu-hotplug "locking"
> implementation.
Uggh. This introduces a global lock that has to be taken always when
scanning over cpus? Is multipe cpus are scanning over processor lists then
we will get into scaling problems. Wasnt there an RCU based implementation
that avoided cacheline bouncing and refcounting?
> The patchstack which is based against 2.6.23-mm1 has behaved well
> when it was stress tested with kernbench running while continuously
> performing cpu-hotplug operations on i386, x86_64 and ppc64.
What was the highest cpu count in testing?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists