From owner-freebsd-current@FreeBSD.ORG Thu Aug 7 20:45:42 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02429106566B; Thu, 7 Aug 2008 20:45:42 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id BB8048FC16; Thu, 7 Aug 2008 20:45:41 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m77Kjblk084519; Thu, 7 Aug 2008 16:45:37 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m77KjaGO098913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Aug 2008 16:45:36 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200808072045.m77KjaGO098913@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 07 Aug 2008 16:45:37 -0400 To: Patrick =?iso-8859-1?Q?Lamaizi=E8re?= From: Mike Tancsa In-Reply-To: <200808070234.m772YFvH094515@lava.sentex.ca> References: <20080606234135.46144207@baby-jane-lamaiziere-net.local> <20080706115414.GA20076@gw.reifenberger.com> <20080706234231.3d18e15a@baby-jane-lamaiziere-net.local> <200808070234.m772YFvH094515@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: pjd@freebsd.org, current@freebsd.org Subject: Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2008 20:45:42 -0000 At 10:34 PM 8/6/2008, Mike Tancsa wrote: >At 05:42 PM 7/6/2008, Patrick Lamaizi=E8re wrote: > >>I think that the driver is ready and works fine, i didn't change >>anything since the latest version "22/06/08" >>http://user.lamaiziere.net/patrick/glxsb-220608.tar.gz > >Hi, > I was doing some testing with openvpn=20 > and was wondering if there is perhaps a memory leak ? > >Doing, >openvpn --test-crypto --secret key --engine=20 >cryptodev --cipher aes-128-cbc > /dev/null > >seems to make the memory in use constantly go up > >0[nanobsdr7]# vmstat -h -m | egrep "Type|glx" > Type InUse MemUse HighUse Requests Size(s) > glxsb_data 1381 173K - 1381 128 >0[nanobsdr7]# >.... >0[nanobsdr7]# vmstat -h -m | egrep "Type|glx" > Type InUse MemUse HighUse Requests Size(s) > glxsb_data 1841 231K - 1841 128 >0[nanobsdr7]# > >InUse is always going up ? This is with the driver from the above url. Actually, the padlock driver shows the same=20 behaviour. Over time, its usage continues to grow Type InUse MemUse HighUse Requests Size(s) padlock_data 4048 4048K - 4048 1024 Type InUse MemUse HighUse Requests Size(s) padlock_data 4056 4056K - 4056 1024 Or am I reading vmstat wrong ? ---Mike=20