2.1.131 isn't quite it for me

Nicolai Langfeldt (janl@math.uio.no)
06 Dec 1998 19:38:26 +0100


Hi,

Plain 2.1.131 + tulip-0.89H-drop-in. Dual PII-350 with 512M RAM and
SMP kernels. I've found these problems:

- NFS write performance it _horrid_. 50-100% worse than under
2.0.36. The server is Dec-Unix 4.0D. The machines are connected
by 100Mbit switched ethernet. Using

dd bs=8k count=1024 if=/dev/zero of=bench

as a benchmark 2.1.131 starts out at 1m40s to write the file,
when repeated the time increases by 5-10 seconds each time,
the load has a tendency to increase above 1 as well but top
showed no clear cpu eater.

Rebooted with mem=64M. The write took ~2m and stayed stable.

MM related?

Linux 2.0.36 on the same machine never uses more than 1m15s to
write the file and the time tends to decrease.

Earlier in the 2.1 cycle (this summer I think it was) I saw
NFS-writing at 2x-3x speed-up relative to 2.0. I have not used
2.1 kernels on these machines since so I have no idea when the
performance dropped.

- Can't get PS/2 port to be recognized at all, as module or
linked in the kernel. It worked under 2.1.130 which I used
some hours last week, it also works under 2.0. Under 2.1.131
this is the config:

# CONFIG_MS_BUSMOUSE is not set
CONFIG_PSMOUSE=m
CONFIG_82C710_MOUSE=y
# CONFIG_PC110_PAD is not set

This is 2.0.36:

# CONFIG_MS_BUSMOUSE is not set
CONFIG_PSMOUSE=m
CONFIG_82C710_MOUSE=y
# CONFIG_UMISC is not set

The 82c710 thing is needed to get the port recognized under 2.0.

Soundblaster sound works though :-)

Nicolai

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/