In my eyes, there must be
a problem with the mkiss driver,
I have had my linux-box up for 19 hours, and mkiss has used 2 hours of
processor time! That is quite a ratio!
Here is a procinfo for the machine:
Linux 2.1.89 (root@irony) (gcc 2.7.2.3) #11 Wed Apr 1 22:07:42 CST 1998
[chaos]
Memory: Total Used Free Shared Buffers
Cached
Mem: 6472 6064 408 1636 148
1668
Swap: 10876 2760 8116
Bootup: Wed Apr 01 23:54:08 1998 Load average: 0.24 0.20 0.20 2/43 1294
user : 0:07:24.67 0.6% page in : 103401 disk 1: 37586r
21546w
nice : 0:00:00.00 0.0% page out: 29449
system: 0:12:26.21 1.1% swap in : 9036
idle : 18:44:47.74 98.3% swap out: 5572
uptime: 19:04:38.58 context : 1469652
irq 0: 6867862 timer irq 8: 0
irq 1: 2 keyboard irq 9: 0
irq 2: 0 cascade [4] irq 10: 0
irq 3: 0 irq 11: 0
irq 4: 2955171 serial irq 12: 0
irq 5: 56651 NE2000 irq 13: 0 fpu
irq 6: 3 irq 14: 353348 hd
irq 7: 0 irq 15: 0
here is /proc/cpuinfo:
processor : 0
cpu family : 3
model : unknown
vendor_id : unknown
stepping : unknown
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
fpu : no
fpu_exception : no
cpuid level : -1
wp : no
flags :
bogomips : 4.56
-----------
it is a 386-33 with 8 mb ram. I have the serial port running at 19200 to
a KPC 9612.
Is this normal for mkiss?
/--------------------------------------------\
| Kirk Wolff lzh@kerailya.tunkki.fi
|
| "Well, that was a piece of cake, eh K-9?"
|
| "Piece of cake, Master? Radial slice of baked confection ...
| coefficient of relevance to Key of Time: zero."
\ -- Dr. Who