Re: mec and resets

[email protected] wrote:

> I can't reproduce it either, my O2 ( R5k with 1MB cache ) also built  
> KDE and X over nfs without any trouble.
> 
> > Is it on GENERIC32_IP3x or some customized kernel?
> 
> Customized as in stripped of anything I don't need. So, basic O2  
> hardware plus ohci and ehci, compiled with -march=mips3

BTW, does your kernel have "options MACE_NEEDS_DELAYS"?

On my R5k O2, a patched kernel without the options MACE_NEEDS_DELAYS
works fine, and it's much faster than one with the option.
i.e. MACE_NEEDS_DELAYS makes mec(4) much slower:

---
on GENERIC32_IP3x:

% ttcp -ts mirage
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  -> mirage
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 4.69 real seconds = 3490.38 KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 2.35, calls/sec = 436.30
ttcp-t: 0.0user 3.5sys 0:04real 76% 0i+0d 0maxrss 0+2pf -4+37csw
% ttcp -rs
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-r: accept from 192.168.20.1
ttcp-r: 16777216 bytes in 4.02 real seconds = 4079.01 KB/sec +++
ttcp-r: 2050 I/O calls, msec/call = 2.01, calls/sec = 510.37
ttcp-r: 0.0user 1.4sys 0:04real 37% 0i+0d 0maxrss 0+2pf -8+31csw
% 

---
GENERIC32_IP3x without "options MACE_NEEDS_DELAYS":

% ttcp -ts mirage
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp  -> mirage
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 2.17 real seconds = 7538.66 KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 1.09, calls/sec = 942.33
ttcp-t: 0.0user 1.4sys 0:02real 66% 0i+0d 0maxrss 0+2pf -3+18csw
% ttcp -rs
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001  tcp
ttcp-r: socket
ttcp-r: accept from 192.168.20.1
ttcp-r: 16777216 bytes in 1.75 real seconds = 9347.64 KB/sec +++
ttcp-r: 2054 I/O calls, msec/call = 0.87, calls/sec = 1171.88
ttcp-r: -1.9user 0.6sys 0:01real 35% 0i+0d 0maxrss 0+2pf -1+15csw
% 

---
Izumi Tsutsui