Re: [Fwd: Interrupts question]

2006-07-19 Thread Oliver Fromme
Alex Zbyslaw wrote: John Baldwin wrote: There's no easy answer on this. You'll have to run your own benchmarks. If you don't need USB, then you may just want to leave it out of your kernel which might help some. OK, thanks for the info and suggestions. Regrettably, leaving

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 aes256

Re: [Fwd: Interrupts question]

2006-07-19 Thread Alex Zbyslaw
Oliver Fromme wrote: Alex Zbyslaw wrote: John Baldwin wrote: There's no easy answer on this. You'll have to run your own benchmarks. If you don't need USB, then you may just want to leave it out of your kernel which might help some. OK, thanks for the info and suggestions.

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, 213

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: swiN: clock sio process taking 75% CPU

2006-07-19 Thread victor cruceru
Hi Gareth, Did you try to disable the console screensaver? Sometimes this helps. Message: 1 Date: Tue, 18 Jul 2006 13:17:32 +0100 From: Gareth McCaughan [EMAIL PROTECTED] Subject: swiN: clock sio process taking 75% CPU To: freebsd-hackers@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type:

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 enable

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:

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. How about

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 used by

more if_tun frustration.

2006-07-19 Thread David Gilbert
To recap, I have tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500 inet6 fe80::214:22ff:fede:f175%tun0 prefixlen 64 scopeid 0x5 inet 192.168.12.2 -- 192.168.22.1 netmask 0x Opened by PID 15236 And I see: [4:18:[EMAIL PROTECTED]:/usr/home/dgilbert

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

Re: On the use of Tun interfaces.

2006-07-19 Thread Stefan Bethke
Am 18.07.2006 um 06:39 schrieb David Gilbert: [3:15:[EMAIL PROTECTED]:~/devel/failsafe netstat -rn ... 192.168.22.1 192.168.12.2 UH 00 tun0 shouldn't the last route there be active? Any clues here? The last time I tried to get a tun interface set up

Re: swiN: clock sio process taking 75% CPU

2006-07-19 Thread John Baldwin
On Wednesday 19 July 2006 12:11, Gareth McCaughan wrote: (The particular screen saver I turned on was the one called warp; I haven't checked yet whether others have the same CPU-guzzling effect.) Actually, if you could test that, that would be helpful as that would narrow down where the bug is

Re: swiN: clock sio process taking 75% CPU

2006-07-19 Thread Gareth McCaughan
On Tuesday 2006-07-18 19:41, John Baldwin wrote: On Tuesday 18 July 2006 13:04, Gareth McCaughan wrote: On Tuesday 2006-07-18 16:54, Deomid Ryabkov wrote: Gareth McCaughan wrote: About 6 minutes after booting (on three occasions, but I don't guarantee this doesn't vary), a

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 in-kernel access

Re: kern/99979: Get Ready for Kernel Module in C++

2006-07-19 Thread David Nugent
Matthias Andree wrote: Deciding that some features are bad beforehand, before you evaluate them is IMO bad idea. Let interested people write a bunch of C++ modules with the complete language before deciding on what shouldn't be used. No, that won't work -- plus you need a bunch of

RE: [Fwd: Interrupts question]

2006-07-19 Thread John Polstra
On 17-Jul-2006 Alex Zbyslaw wrote: I was monitoring a machine with systat -vmstat and noticed something about the interrupts and I don't know if it's a problem or not. If it is a problem, is there anything I can do about it? The interrupts for the network interface (em0) on irq 64 exactly