From owner-freebsd-stable@FreeBSD.ORG Thu Aug 7 00:40:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A6411065672 for ; Thu, 7 Aug 2008 00:40:55 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 550038FC16 for ; Thu, 7 Aug 2008 00:40:55 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m770es5V063400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 6 Aug 2008 17:40:54 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <489A4496.2060602@freebsd.org> Date: Wed, 06 Aug 2008 17:40:54 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20080806201144.GB1554@roadrunner.spoerlein.net> In-Reply-To: <20080806201144.GB1554@roadrunner.spoerlein.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-Misty-Metrics: ebb.errno.com; whitelist Subject: Re: What is cryptosoft0? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 07 Aug 2008 00:40:55 -0000 Ulrich Spoerlein wrote: > Hi, > > today I discovered the following dmesg line on my laptop: > > cryptosoft0: on motherboard > > and I've not seen this one before, so: what is cryptosoft and should I > care? > > I could imagine it's a pseudo-device by crypto(9) so the API is the same > whether crypto hardware is installed or not. > > Anyway, I think a manpage link/update would be in order: > > % man -k cryptosoft > cryptosoft: nothing appropriate > > It is what you suggest; a device associated with s/w crypto support. It was created so crypto requests can be submitted specifically to it (instead of a h/w device). This is currently used only for testing but the intent was also to use it when doing load-balancing and similar work. Sam