From owner-freebsd-current@FreeBSD.ORG  Fri Mar 27 20:29:22 2015
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0061CEE6;
 Fri, 27 Mar 2015 20:29:21 +0000 (UTC)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com
 [IPv6:2607:f8b0:4001:c05::232])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B82A7D9;
 Fri, 27 Mar 2015 20:29:21 +0000 (UTC)
Received: by igbqf9 with SMTP id qf9so30085650igb.1;
 Fri, 27 Mar 2015 13:29:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=hpb9ZYiYRqcadZ4s0Bc//fEHWUnb8pLeK2dhni+0Lv8=;
 b=l2039C7LRsvjKFfL9Kok13bXJ3Ixy6K6wpcw5qXlyaHBkP+7G63L5a3zGTcQiogQZy
 nNZLuu/D+XZql0oAduNUf7CbAFLXH45tQORgE5FN6lKAxFK0dPHKv4FPIQ/oiIzBZlOg
 sn/M9kSZwYuqHrKsgoMy5s60KC6nXb1lEFzqHYowxAH8S2wwTvM3ImBF6tQ0DajcF7Wj
 UgzMypKzr1HAJsw9FzCHD7UlEW41xisXzumA0CKpAyxccRkLDST0ZAMd5+yJVsYN/vsu
 wKSZGZrolip39k5LGSo5CQ70o3o2C1TYP7cGeGkJ/0PgFS0wZrAHza5sCDEvQhpn4XKG
 sX5g==
MIME-Version: 1.0
X-Received: by 10.50.143.42 with SMTP id sb10mr905530igb.49.1427488160609;
 Fri, 27 Mar 2015 13:29:20 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.36.17.194 with HTTP; Fri, 27 Mar 2015 13:29:20 -0700 (PDT)
In-Reply-To: <5515AED9.8040408@FreeBSD.org>
References: <5515AED9.8040408@FreeBSD.org>
Date: Fri, 27 Mar 2015 13:29:20 -0700
X-Google-Sender-Auth: MgFXCS5mBruPrnyD41mzR0ldZQw
Message-ID: <CAJ-VmomQ6vMCOOsc2128M4TJtUKhmieo3_Bf75MYB6p4tS85jA@mail.gmail.com>
Subject: Re: SSE in libthr
From: Adrian Chadd <adrian@freebsd.org>
To: Eric van Gyzen <vangyzen@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: "current@freebsd.org" <current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Mar 2015 20:29:22 -0000

Wow. I remember seeing this in the work application - all packet
pushing in userland, but there are locks being acquired. I was
wondering what exactly was triggering the FPU save/restore code. Now I
know.

Yes, if there are no other objections, I'd love to see this in -HEAD
and stable/10.


-adrian