Re: [Dovecot] testing needed: log file concurrency

2007-06-21 Thread Johannes Berg
On Wed, 2007-06-20 at 02:41 +0300, Timo Sirainen wrote: - SMP kernels: page size cut once in a while exactly what happens with Linux 2.6.22-rc5 on my quad powermac johannes signature.asc Description: This is a digitally signed message part

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread greg
Hi Timo, http://dovecot.org/tmp/concurrency.c [cut] So far I've tested only with Linux 2.6.21 x86-64/SMP and a slow Solaris/Sparc/UP. One writer and three readers ran for 30 minutes on Solaris 10 without printing anything. The box is an UltraSparc IIIi dual proc, and the FS on the partition

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Sascha Holzleiter
On Wed, Jun 20, 2007 at 02:41:42AM +0300, Timo Sirainen wrote: http://dovecot.org/tmp/concurrency.c I'd want to know what results this program gives with different systems. Please test and reply (but don't bother if someone already replied with the same OS+result). I expect it to print:

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Tan Shao Yi
Hi Timo, It prints the following: ./concurrency writing, page size = 8192 ./concurrency 1 reading, page size = 8192 This is a: SunOS 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-V240 psrinfo -v Status of virtual processor 0 as of: 06/20/2007 21:00:33 on-line since 04/05/2007

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Bill Boebel
On Tue, June 19, 2007 7:41 pm, Timo Sirainen [EMAIL PROTECTED] said: http://dovecot.org/tmp/concurrency.c I'd want to know what results this program gives with different systems. Please test and reply (but don't bother if someone already replied with the same OS+result). I expect it to

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Timo Sirainen
On Wed, 2007-06-20 at 02:41 +0300, Timo Sirainen wrote: http://dovecot.org/tmp/concurrency.c I'd want to know what results this program gives with different systems. Please test and reply (but don't bother if someone already replied with the same OS+result). I expect it to print: - SMP

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread David Favor
Timo Sirainen wrote: On Wed, 2007-06-20 at 02:41 +0300, Timo Sirainen wrote: http://dovecot.org/tmp/concurrency.c Works on dual processor running latest Fedora 7: net1#uname -a Linux net1.coolsurf.com 2.6.21-1.3228.fc7 #1 SMP \ Tue Jun 12 14:56:37 EDT 2007 x86_64 x86_64 x86_64

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Troy Engel
OS: CentOS 4.5 (Final) (RHEL4 clone) $ /usr/bin/time -f total time: %E\ni/o waits: %w\n ./concurrency writing, page size = 4096 Command terminated by signal 2 total time: 10:41.53 i/o waits: 312177 $ /usr/bin/time -f total time: %E\ni/o waits: %w\n ./concurrency 1 reading, page size = 4096 page

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Timo Sirainen
On Wed, 2007-06-20 at 02:41 +0300, Timo Sirainen wrote: http://dovecot.org/tmp/concurrency.c You can forget about this for now. There was one bug in it and with a couple of changes I can't break it in my own system either anymore. Wonder why I'm seeing similar problems in Dovecot v1.1 code..

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Gunter Ohrner
Am Mittwoch, 20. Juni 2007 schrieb Timo Sirainen: http://dovecot.org/tmp/concurrency.c Mh... 19:51:35 FEHLER 404: Not Found. I just wanted to test it using Linux 2.6.21 on my Core2 Duo T7200 running Debian Unstable... Does anyone still have the file? Greetings, Gunter -- *** Powered

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Timo Sirainen
On Wed, 2007-06-20 at 20:11 +0300, Timo Sirainen wrote: On Wed, 2007-06-20 at 02:41 +0300, Timo Sirainen wrote: http://dovecot.org/tmp/concurrency.c You can forget about this for now. There was one bug in it and with a couple of changes I can't break it in my own system either anymore.

Re: [Dovecot] testing needed: log file concurrency

2007-06-20 Thread Gunter Ohrner
Am Mittwoch, 20. Juni 2007 schrieb Gunter Ohrner: Am Mittwoch, 20. Juni 2007 schrieb Timo Sirainen: http://dovecot.org/tmp/concurrency.c Does anyone still have the file? Ok, there was a race between Thimos and my mails... ;) Greetings, Gunter -- *** Powered by AudioScrobbler --

[Dovecot] testing needed: log file concurrency

2007-06-19 Thread Timo Sirainen
http://dovecot.org/tmp/concurrency.c I'd want to know what results this program gives with different systems. Please test and reply (but don't bother if someone already replied with the same OS+result). I expect it to print: - SMP kernels: page size cut once in a while - UP (uniprocessor)

Re: [Dovecot] testing needed: log file concurrency

2007-06-19 Thread Adam McDougall
If there is no output, whats the longest you want us to wait while it runs? How much do you care about unique OS/arch/cpu/fs combinations (what factors shouldn't matter)? I assume you want just one reader and one writer, started in the order listed in the source? I currently have it running on

Re: [Dovecot] testing needed: log file concurrency

2007-06-19 Thread Timo Sirainen
On Tue, 2007-06-19 at 20:16 -0400, Adam McDougall wrote: If there is no output, whats the longest you want us to wait while it runs? I think if it hasn't printed anything for 15 minutes it's pretty safe to assume it's not going to print anything. How much do you care about unique

Re: [Dovecot] testing needed: log file concurrency

2007-06-19 Thread Luigi Rosa
Timo Sirainen said the following on 20/6/2007 1:41: http://dovecot.org/tmp/concurrency.c AMD Athlon(tm) 64 Processor 2800+ 2.6.21-1.3228.fc7 (Fedora 7) Noting. Intel(R) Pentium(R) 4 CPU 3.06GHz w/HyperThreading 2.6.9-42.0.3.ELsmp (Red Hat) page size cut after a couple of minutes Ciao,

Re: [Dovecot] testing needed: log file concurrency

2007-06-19 Thread Adam McDougall
On Wed, Jun 20, 2007 at 03:31:21AM +0300, Timo Sirainen wrote: On Tue, 2007-06-19 at 20:16 -0400, Adam McDougall wrote: If there is no output, whats the longest you want us to wait while it runs? I think if it hasn't printed anything for 15 minutes it's pretty safe to assume it's