From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 29 20:47:03 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C34C75D7 for ; Tue, 29 Oct 2013 20:47:03 +0000 (UTC) (envelope-from trev@larock.ca) Received: from dpmailmta01.doteasy.com (dpmailmta01-17.doteasy.com [65.61.218.17]) by mx1.freebsd.org (Postfix) with ESMTP id 8F936258E for ; Tue, 29 Oct 2013 20:47:03 +0000 (UTC) Received: from dpmail22.doteasy.com ([192.168.101.22]) by dpmailrp04.doteasy.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id r9TKUfDl008660 for ; Tue, 29 Oct 2013 13:30:41 -0700 Received: from mail-lb0-f177.google.com [209.85.217.177] by dpmail22.doteasy.com with SMTP; Tue, 29 Oct 2013 13:30:34 -0700 Received: by mail-lb0-f177.google.com with SMTP id u14so476759lbd.36 for ; Tue, 29 Oct 2013 13:30:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=ln7LjdYaPbRPKW549WXzLoXBKcKtAdsul32mSaN7mZ4=; b=jP4qItMrO89jsXghBkGOFiY8QSOvpDe5/0NMX1kT/8/ZFi8U+ibQ5QkwYdeWBTsyn1 YzUwQdJ/qcaESoBqd/PI4JgOrcQXqMkcZPcqStOzWMHpyjRMqskhzHZuG0tc3jtsXaxH oU13BEdEsdxED1o4oUeYZcAxAay2iOs/z9uQ88yUAuKOILggCX7F8AC+Uyd37s5DWBS3 T8U4mLpKuirBBtWQCYv8r372UcLiJBRBFxsGVOQI/FD662fYi+j2wSoDGypIdarG201t lGSg9Vo6IngWM++83dkRQMqO9EKjVaGdGOLIWnLSOguvn82LH8A86/dkbGUHc6wqciS/ CGQA== MIME-Version: 1.0 X-Received: by 10.152.10.34 with SMTP id f2mr69264lab.64.1383078628855; Tue, 29 Oct 2013 13:30:28 -0700 (PDT) Received: by 10.112.35.197 with HTTP; Tue, 29 Oct 2013 13:30:28 -0700 (PDT) Date: Tue, 29 Oct 2013 16:30:28 -0400 Message-ID: Subject: AES-GCM in kernel From: "trev@larock.ca" To: freebsd-hackers@freebsd.org X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN, base:default) X-Spam-Score: 0.10 () [Hold at 5.00] HTML_MESSAGE:0.001, RDNS_NONE:0.1, TO_NO_BRKTS_NORDNS:0.001 X-CanIt-Geo: No geolocation information available for 192.168.101.22 X-CanItPRO-Stream: base:default X-Canit-Stats-ID: 05KH8uFE2 - b69c619a4a62 - 20131029 X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.168.101.84 X-Originating-IP: 192.168.101.84 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 20:47:03 -0000 Hi, I was interested to know more about AES-GCM plans for the kernel. I have seen a few posts about patches that might get committed but there didn't seem to be further discussion. Any related info/roadmap plans? Thanks, Trev Larock _______________________________________________________ Unlimited Disk, Data Transfer, PHP/MySQL Domain Hosting http://www.doteasy.com From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 29 21:11:46 2013 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0DCA9D84; Tue, 29 Oct 2013 21:11:46 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2B30A2803; Tue, 29 Oct 2013 21:11:44 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA15681; Tue, 29 Oct 2013 23:11:43 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VbGZj-0005x6-9I; Tue, 29 Oct 2013 23:11:43 +0200 Message-ID: <5270246B.6070105@FreeBSD.org> Date: Tue, 29 Oct 2013 23:11:07 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: dtrace@FreeBSD.org Subject: sdt "sname" removal X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 21:11:46 -0000 I never understood why FreeBSD SDT as opposed to upstream SDT requires the same or almost the same probe name to be specified twice. This seems to be silly and a little bit error-prone. In other words, I do not see any reason not to re-use the original upstream trick where double underscore in a providers name in the C code gets converted to a single dash in a DTrace provider name. [*] So here is my take at that: http://people.freebsd.org/~avg/sdt-sname-removal.diff An inline preview of the change: -SDT_PROBE_DEFINE1(priv, kernel, priv_check, priv_ok, priv-ok, "int"); -SDT_PROBE_DEFINE1(priv, kernel, priv_check, priv_err, priv-err, "int"); +SDT_PROBE_DEFINE1(priv, kernel, priv_check, priv__ok, "int"); +SDT_PROBE_DEFINE1(priv, kernel, priv_check, priv__err, "int"); It's possible that I missed some places where old style SDT_PROBE_DEFINE macros are used or where an old probe name is used with SDT_PROBE_ARGTYPE or SDT_PROBE. Please test, review, comment, etc. Thank you! -- Andriy Gapon