From owner-freebsd-stable@freebsd.org Thu Dec 6 23:04:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B86A213178A0 for ; Thu, 6 Dec 2018 23:04:54 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-it1-x129.google.com (mail-it1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F147D86BF6 for ; Thu, 6 Dec 2018 23:04:53 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-it1-x129.google.com with SMTP id i145so4147859ita.4 for ; Thu, 06 Dec 2018 15:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=hQPB6xmQWQebTlIudnOrmywThO8x5rpZgDMSM4/xIpY=; b=pJv1vuz36cRo500PO44CVZCV0twxvp59c6LLWKWqkL78HwhYN1I/tzpb2qLFoey89Z pixKs7caMw2y7fUNyml3whnRSV6Jy1T5xI+E4Dx0owovWKt2BRiPLKSAj+KiPC0te/nN gqJIrAbzigIBGbm8KDZSdVKC3a9N4juooPYUlJzew9pS/kBCvh401hNqrIIg2LCbfVZ+ Ofi2IyyfH+kjxNUyiSR0wk+Wm7RWd57zrpm1ZTFPhjvGRbV/EflWWkLip6RRkqSQxD7I uvcqSG31G76eb9i75mIES5SX5htQTqriU97+Euh05vbBllIxL/5u8hwzELfCRszARMfm iBYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=hQPB6xmQWQebTlIudnOrmywThO8x5rpZgDMSM4/xIpY=; b=LLq3CV2O6HrQm55qKQcSqnLj+5QwF6dsjrIjrLtFiddkKzVnX/v2wGtfHYofxkm1H9 ZJJ1qfP+8xRsxjLvzBAB2DFyJFKd1FihjyUuGfbM6zVp5A2D/jESzPymCGko2yHSHjmJ IfpjNMErNaNkqHwq3N/e89adJQoAHTMWJmcOvPiTb/2q32NB2uAogi+E0oaQzLayy4mz 7kjgizeQlSJjb7BVDsJCUBcS7NiUk8tZxTZgkeTe/RdbytwJ6MZ116sc85hvj4X/GBEm tBnDUvC+TlnEUge1lwBZ9Z1VnoFmoa7H3+cNg1hvjNh4DRPsk87cnZ1WotxACkFZz61B L61Q== X-Gm-Message-State: AA+aEWaxOWFPcN/anpXjZuq1S+9uMG/5yvi2v3daw0F4D3V5okrYeHwM gCX4z4DImTrbGX9lEEBBmA1DVM6mot/M+n3g2B2gUJz3 X-Google-Smtp-Source: AFSGD/VkVB/UJ8VCv9PeyZUfHyWRLkRT523ZZPtBxhq46eDajJL8yaJajg2AEJW6XRLzb4xie5e0Ra3WqLzjTRgnAm0= X-Received: by 2002:a24:5953:: with SMTP id p80mr282130itb.46.1544137492963; Thu, 06 Dec 2018 15:04:52 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Xin LI Date: Thu, 6 Dec 2018 15:04:41 -0800 Message-ID: Subject: Re: /dev/crypto not being used in 12-STABLE To: lists@jnielsen.net Cc: FreeBSD Stable Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: F147D86BF6 X-Spamd-Result: default: False [-6.17 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[9.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.99)[-0.989,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; IP_SCORE(-2.18)[ip: (-7.93), ipnet: 2607:f8b0::/32(-1.54), asn: 15169(-1.31), country: US(-0.09)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Dec 2018 23:04:55 -0000 On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: > > I have upgraded two physical machines from 11-STABLE to 12-STABLE recentl= y (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391)= . I noticed today that neither machine seems to be utilizing /dev/crypto. T= ypically I see at least ssh/sshd have the device open plus some programs fr= om ports. But 'fuser' doesn't list any processes on either machine: > > # fuser /dev/crypto > /dev/crypto: > > Both machines are running custom kernels that include "device crypto" and= "device cryptodev". One of them additionally has "device aesni". > > Is anyone else seeing this? Any idea what would cause it? Your average OpenSSL applications should not use /dev/crypto, if your goal is to utilize AES-NI (which does not require /dev/crypto). On capable systems, AES-NI would be used automatically (and it's faster this way). Cheers,