On Sun, 08 Jan 2006 11:23:37 +0100, [email protected] (Bernd Eckenfels) wrote:
>Willy Tarreau <[email protected]> wrote:
>> It's rather strange that 2.6 *eats* CPU apparently doing nothing !
>
>it eats it in high interrupt load. And it is caused by the pty-ssh-tcp
>output, so most likely those are eepro100 interrupts.
That would be true for either 2.4 or 2.6, no? Also it runs e100
driver, but...
2.4 dmesg:
Intel(R) PRO/100 Network Driver - version 2.3.43-k1
Copyright (c) 2004 Intel Corporation
e100: selftest OK.
e100: eth0: Intel(R) PRO/100 Network Connection
Hardware receive checksums enabled
cpu cycle saver enabled
2.6 dmesg:
[ 31.977945] e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
[ 31.978007] e100: Copyright(c) 1999-2005 Intel Corporation
[ 32.002928] e100: eth0: e100_probe: addr 0xfd201000, irq 11, MAC addr 00:90:27:42:AA:77
[ 32.026992] e100: eth1: e100_probe: addr 0xfd200000, irq 12, MAC addr 00:90:27:58:32:D4
[ 32.186941] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Are rx checksums not turned on in 2.6' e100 driver?
CPU is only pentium/mmx 233
--
Thanks,
Grant.
http://bugsplatter.mine.nu/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
