Re: AMD Geode LX crypto accelerator (glxsb) (and padlock.ko)

At 10:34 PM 8/6/2008, Mike Tancsa wrote:
>At 05:42 PM 7/6/2008, Patrick Lamaizière 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 
> and was wondering if there is perhaps a memory leak ?
>
>Doing,
>openvpn --test-crypto --secret key --engine 
>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 
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