From owner-freebsd-stable@FreeBSD.ORG Tue Mar 24 23:26:10 2015 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:1900:2254:206a::19:2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6EDBC5A; Tue, 24 Mar 2015 23:26:10 +0000 (UTC) Received: from hammer.pct.niksun.com (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx2.freebsd.org (Postfix) with ESMTP id 0C483E5B; Tue, 24 Mar 2015 23:26:09 +0000 (UTC) Message-ID: <5511F291.3070202@FreeBSD.org> Date: Tue, 24 Mar 2015 19:26:09 -0400 From: Jung-uk Kim User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Konstantin Belousov , Mike Tancsa Subject: Re: RELENG_10 performance regression (was Re: 35-40% performance drop releng9 vs releng10 openvpn References: <5509D6C6.4050204@sentex.net> <20150318211457.GL51048@funkthat.com> <550B6950.8060806@sentex.net> <550C5AAF.9060502@sentex.net> <550C8AEE.4090408@sentex.net> <550CB306.7030405@delphij.net> <20150321001559.GB2379@kib.kiev.ua> <550CBF80.6030809@sentex.net> <550D93C7.9080709@FreeBSD.org> <550DB4B2.7080603@sentex.net> <20150321184238.GO2379@kib.kiev.ua> In-Reply-To: <20150321184238.GO2379@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: FreeBSD-STABLE Mailing List , John-Mark Gurney , d@delphij.net, John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2015 23:26:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 03/21/2015 14:42, Konstantin Belousov wrote: > It seems to be a consequnce of the code from r222869. The > test_tsc() does not trust the P-state invariant report and > explicitely check for the family. Your CPU family is 0x14, while > code only bumps TSC priority for family 0x15+. We need to find out whether the Bobcat cores have well-synchronized TSCs. If it does, we can white-list it, too. However, I doubt it. Sorry for the late response, Jung-uk Kim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVEfKMAAoJEHyflib82/FGZUgH/RZ8LBBeW2ue+0SIJj8Er9Ni uyEA3KJL7ZmdjuGUtOdDl3s3cwHcTxbKN39rdabjOyJy/OoNnJK3GfL8UgYSpERa ztdHHNLbxJK9Z3iN7rvjXxQMHBJy3D4LIQ9BXFau3xcO7K8WDXqdHjUZx/ujrSpU WwDoZRFohvUf2FT1J23NfWBOx0Mnls3PrQm4f6YLhVst6RojDgx8XA24LyIm+AkF WUZcPttydp9nde1Hc7qyFI5qB3ZMhT1tG9jp+J2jQWeqCn/SPR3VymF+Lyz/T0sC POEa6NTJf4lWXOHRZ21Fdkrtr1hBltdO1FImX9M2iNlyRwz57UsNW6yJawGhYJA= =w6Hk -----END PGP SIGNATURE-----