From owner-freebsd-threads@FreeBSD.ORG  Thu Dec  4 14:43:39 2014
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C39FEA3F
 for <freebsd-threads@FreeBSD.org>; Thu,  4 Dec 2014 14:43:39 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id AB9C4E10
 for <freebsd-threads@FreeBSD.org>; Thu,  4 Dec 2014 14:43:39 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sB4EhdaL049214
 for <freebsd-threads@FreeBSD.org>; Thu, 4 Dec 2014 14:43:39 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 195098] pthread lock performance degradation
Date: Thu, 04 Dec 2014 14:43:39 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: emaste@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-195098-16-YLxDAVNmbn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195098-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-195098-16@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads/>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2014 14:43:39 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195098

--- Comment #1 from Ed Maste <emaste@freebsd.org> ---
Thank you for the self-contained test case.

Unfortunately I am not able to reproduce this on any of:

FreeBSD 11.0-CURRENT up to date as of Nov 21 2014 (i5-2540M laptop bare metal)
FreeBSD 10.1-RC2 (i7-3770 desktop bare metal)
FreeBSD 10.0-RELEASE (VM image from http://nongnu.org/pretest/ under bhyve)

I see from the bug-gnulib list that this has been observed running the FreeBSD
image under Linux KVM. Is that common to all reproduction cases?

-- 
You are receiving this mail because:
You are the assignee for the bug.