Re: VIA padlock performance

2006-07-19 Thread Jesse Ahrens
There's no locking in the hardware, all the xcrypt commands are ring3 accessible. Shouldn't be an issue to use either. > Michael Reifenberger wrote: > > On Wed, 19 Jul 2006, Oliver Fromme wrote: > > ... > > > You will also need "cryptodev" in addition to "crypto". > > > "crypto" manages only i

Re: VIA padlock performance

2006-07-19 Thread Michael Reifenberger
On Wed, 19 Jul 2006, Christian Brueffer wrote: ... Something like the attached patch? I'd prefer a more compact version. How about the attached patch? Also applies some more word smithing. commited. Thanks! Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Con

Re: VIA padlock performance

2006-07-19 Thread Oliver Fromme
Michael Reifenberger wrote: > On Wed, 19 Jul 2006, Oliver Fromme wrote: > ... > > You will also need "cryptodev" in addition to "crypto". > > "crypto" manages only in-kernel access to the cryptographic > > facilities (including hardware acceleration through the > > padlock driver), which is u

Re: VIA padlock performance

2006-07-19 Thread Christian Brueffer
On Wed, Jul 19, 2006 at 05:13:29PM +0200, Michael Reifenberger wrote: > On Tue, 18 Jul 2006, Christian Brueffer wrote: > ... > > > >Nice, could you update padlock(4) with information about supported C7 > >processors? > > > > Something like the attached patch? > I'd prefer a more compact version.

Re: VIA padlock performance

2006-07-19 Thread Michael Reifenberger
On Tue, 18 Jul 2006, Christian Brueffer wrote: ... Nice, could you update padlock(4) with information about supported C7 processors? Something like the attached patch? Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: [EMAIL PROTECTED] | Priv: [EM

Re: VIA padlock performance

2006-07-19 Thread Michael Reifenberger
On Wed, 19 Jul 2006, Oliver Fromme wrote: ... You will also need "cryptodev" in addition to "crypto". "crypto" manages only in-kernel access to the cryptographic facilities (including hardware acceleration through the padlock driver), which is used by FAST_IPSEC, for example. "cryptodev" will ena

Re: VIA padlock performance

2006-07-19 Thread Oliver Fromme
Andrzej Tobola wrote: > Oliver Fromme wrote: > > On my EPIA 1 (1GHz VIA Nehemia) I did some performance > > testing a few months ago under RELENG_6 (not sophisticated > > enough to call it benchmarking). For testing I used scp(1) > > of a large file (an ISO9660 image, 213 MBytes), because

Re: VIA padlock performance

2006-07-19 Thread Andrzej Tobola
Hello Oliver, On Wed, Jul 19, 2006 at 02:06:18PM +0200, Oliver Fromme wrote: > On my EPIA 1 (1GHz VIA Nehemia) I did some performance > testing a few months ago under RELENG_6 (not sophisticated > enough to call it benchmarking). For testing I used scp(1) > of a large file (an ISO9660 image,

Re: VIA padlock performance

2006-07-19 Thread Oliver Fromme
Michael Reifenberger <[EMAIL PROTECTED]> wrote: > with a via epia EN-15000 MB and an U160 scsi disk I get with eli(4) I get > ~27-40MB/s read/write performance trough eli(4) with AES265 key. > > cryptotest gives: > (totum)(root) ./cryptotest -a aes256 10 4096 > 7.838 sec, 20 aes25

Re: VIA padlock performance

2006-07-18 Thread Christian Brueffer
On Tue, Jul 18, 2006 at 11:24:00AM +0200, Michael Reifenberger wrote: > Hi, > with a via epia EN-15000 MB and an U160 scsi disk I get with eli(4) I get > ~27-40MB/s read/write performance trough eli(4) with AES265 key. > > cryptotest gives: > (totum)(root) ./cryptotest -a aes256 10 4096 > 7.8

VIA padlock performance

2006-07-18 Thread Michael Reifenberger
Hi, with a via epia EN-15000 MB and an U160 scsi disk I get with eli(4) I get ~27-40MB/s read/write performance trough eli(4) with AES265 key. cryptotest gives: (totum)(root) ./cryptotest -a aes256 10 4096 7.838 sec, 20 aes256 crypts,4096 bytes, 104511751 byte/sec, 797.4 Mb/sec