Re: poor fdc(4) performance

2005-11-13 Thread Pyun YongHyeon
On Sat, Nov 12, 2005 at 10:14:22AM -0600, Matthew D. Fuller wrote: On Sat, Nov 12, 2005 at 04:44:18PM +0900 I heard the voice of Pyun YongHyeon, and lo! it spake thus: Yes, it could be. But I think the machine is fast enough to read sequential blocks. Try running it without SMP.

Re: poor fdc(4) performance

2005-11-12 Thread Matthew D. Fuller
On Sat, Nov 12, 2005 at 04:44:18PM +0900 I heard the voice of Pyun YongHyeon, and lo! it spake thus: Yes, it could be. But I think the machine is fast enough to read sequential blocks. Try running it without SMP. There may be enough happening in the MP locking bit that you end up falling

poor fdc(4) performance

2005-11-11 Thread Pyun YongHyeon
Hi, I encountered a P3 SMP system that shows poor fdc(4) performance. But when I use larger block size, say 36b, it seems it works as expected. #dd if=boot.flp of=/dev/fd0 2880+0 records in 2880+0 records out 1474560 bytes transferred in 607.483808 secs (2427 bytes/sec) #dd if=boot.flp of=/dev

Re: poor fdc(4) performance

2005-11-11 Thread Peter Jeremy
On Sat, 2005-Nov-12 16:18:15 +0900, Pyun YongHyeon wrote: I encountered a P3 SMP system that shows poor fdc(4) performance. But when I use larger block size, say 36b, it seems it works as expected. 36b is one track. My suspicion is that the system isn't fast enough to read sequential blocks, one

Re: poor fdc(4) performance

2005-11-11 Thread Pyun YongHyeon
On Sat, Nov 12, 2005 at 06:37:11PM +1100, Peter Jeremy wrote: On Sat, 2005-Nov-12 16:18:15 +0900, Pyun YongHyeon wrote: I encountered a P3 SMP system that shows poor fdc(4) performance. But when I use larger block size, say 36b, it seems it works as expected. 36b is one track. My