From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755991Ab2IYL60 (ORCPT ); Tue, 25 Sep 2012 07:58:26 -0400 Received: from merlin.infradead.org ([205.233.59.134]:43076 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755262Ab2IYL6Z convert rfc822-to-8bit (ORCPT ); Tue, 25 Sep 2012 07:58:25 -0400 Message-ID: <1348574286.3881.40.camel@twins> Subject: Re: 20% performance drop on PostgreSQL 9.2 from kernel 3.5.3 to 3.6-rc5 on AMD chipsets - bisected From: Peter Zijlstra To: Linus Torvalds Cc: Mike Galbraith , Borislav Petkov , Mel Gorman , Nikolay Ulyanitsky , linux-kernel@vger.kernel.org, Andreas Herrmann , Andrew Morton , Thomas Gleixner , Ingo Molnar , Suresh Siddha Date: Tue, 25 Sep 2012 13:58:06 +0200 In-Reply-To: References: <20120914212717.GA29307@liondog.tnic> <20120924150048.GB11266@suse.de> <1348500647.11847.69.camel@twins> <1348503163.11847.97.camel@twins> <1348505683.11847.111.camel@twins> <1348511193.6951.44.camel@marge.simpson.net> <20120924192056.GB4082@liondog.tnic> <1348538258.7100.23.camel@marge.simpson.net> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-09-24 at 19:11 -0700, Linus Torvalds wrote: > In the not-so-distant past, we had the intel "Dunnington" Xeon, which > was iirc basically three Core 2 duo's bolted together (ie three > clusters of two cores sharing L2, and a fully shared L3). So that was > a true multi-core with fairly big shared L2, and it really would be > sad to not use the second core aggressively. Ah indeed. My Core2Quad didn't have an L3 afaik (its sitting around without a PSU atm so checking gets a little hard) so the LLC level was the L2 and all worked out right (it also not having SMT helped of course). But if there was a Xeon chip that did add a package L3 then yes, all this would become more interesting still. We'd need to extend the scheduler topology a bit as well, I don't think it can currently handle this well. So I guess we get to do some work for steamroller.