2.4.12-ac4 10Mbit NE2k interrupt load kills p166

2.4.12-ac4 10Mbit NE2k interrupt load kills p166

Post by Samium Gromof » Sat, 27 Oct 2001 05:00:13



       Hello folks...

        Host A: p166, ISA NE2K, linux-2.4.12-ac4
        Host B: p2-400, rtl-8129, WinXP (heh, not my box though ;)

        Load: smbmount connection from host A to the host B, and getting
     large files.

        Result:
                a) modem dies completely - drops ppp packets at the rate of 75%,
                irqtune doesnt affect this behaviour at all

                b) mpg123 sound becomes corrupted, as if its interrupted
                with rate of 100Hz for a very little amount of time,
                irqtune doesnt affect this behaviour at all

                c) CPU load does not depend on whether mpg123 is started,
                ie at the moment mpg123 exits, system cpu usage pops up.

                d) complete stopping sound (killing esd which leads to
                the fact that soundcard stops to emit interrupts), increases
                network copy performance by the factor of 1.2

                e) renicing ksoftirqd doesnt affect the behaviour at all

                f) renicing mc increases copy performance my the factor of 1.2

        Now i`m compiling the 2.4.13-linus to test it either...

cheers, Samium Gromoff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

2.4.12-ac4 10Mbit NE2k interrupt load kills p166

Post by Samium Gromof » Sat, 27 Oct 2001 12:00:06



Quote:> >        Hello folks...

> >       Host A: p166, ISA NE2K, linux-2.4.12-ac4
> >       Host B: p2-400, rtl-8129, WinXP (heh, not my box though ;)

> >       Load: smbmount connection from host A to the host B, and getting
> >      large files.

> You don't say if any of the tests you did are related to smbfs. I suspect
> this reasoning is completely irrelevant (not, that it has stopped me
> before ... :)

> smbfs is not the fastest thing around. I think the slowness on some
> operations is related to how it waits after sending each request.

>      process A                               process B
>    get semaphore
>    request 4096 bytes                      wait on semaphore
>    ... wait for network ...
>    read packet
>    read packet
>    read packet
>    release semaphore
>                                    get semaphore
>                                    request 4096 bytes

> It could send the second request without waiting for the first to complete
> (if it knew how to separate the responses). Doing that should speed things
> up.

> If you play mp3's over smbfs while also doing something else I suppose the
> delay could become noticable. I can't explain the other effects, so
> possibly this is unrelated to smbfs.

> You could make me happy by repeating the tests, but generating the network
> load with something else (http?).

> /Urban

        1. /dev/hda is -u1d1 `ed, and the disc load is near to not existent
        2. mp3 is placed locally

cheers, Samium Gromoff

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. 2.4.12-ac4 10Mbit NE2k interrupt load kills p166

Unfortunately, this will most likely fall under
'almost nobody interested in fiddling with old hw' category...


--
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. changind file permissions for a symbolic link

3. Fwd: VM testing with mtest, 2.4.12-ac3, 2.4.12-ac3+riel's patches, and 2.4.13aa1

4. Solaris 7 on Intel Providence

5. P4 and 2.4.12

6. A few questtions

7. No Sound in 2.4.12

8. HP Openview and Extra! X...

9. Kernel 2.4.12 Compiling error.

10. 3ware 3dmd & 2.4.12-ac: Error: No Controllers Found

11. 2.4.12 cannot find root device on raid

12. 2.4.12-ac3 floppy module requires 0x3f0-0x3f1 ioports

13. another 2.4.12 + aacraid + SuSE failure.