Re: apic patches (with MIS counter)
On Mon, Feb 26, 2001 at 01:14:11PM +0100, Maciej W. Rozycki wrote: > On Mon, 26 Feb 2001, Roeland Th. Jansen wrote: > > if you like, I can start banging the machine on it's head now. > > Please do. I believe the code is safe to be included in 2.4.3, but if > any problem is going to pop up, it'd better do it before than after > applying to the mainstream. banged the box quite a bit. so far no weird things like lockups. still 2.4.1. with the MIS counter (etc) patch. -- Grobbebol's Home | Don't give in to spammers. -o) http://www.xs4all.nl/~bengel | Use your real e-mail address /\ Linux 2.2.16 SMP 2x466MHz / 256 MB |on Usenet. _\_v - 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/
Re: apic patches (with MIS counter)
On Mon, Feb 26, 2001 at 01:14:11PM +0100, Maciej W. Rozycki wrote: On Mon, 26 Feb 2001, Roeland Th. Jansen wrote: if you like, I can start banging the machine on it's head now. Please do. I believe the code is safe to be included in 2.4.3, but if any problem is going to pop up, it'd better do it before than after applying to the mainstream. banged the box quite a bit. so far no weird things like lockups. still 2.4.1. with the MIS counter (etc) patch. -- Grobbebol's Home | Don't give in to spammers. -o) http://www.xs4all.nl/~bengel | Use your real e-mail address /\ Linux 2.2.16 SMP 2x466MHz / 256 MB |on Usenet. _\_v - 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/
Re: apic patches (with MIS counter)
On Mon, Feb 26, 2001 at 01:14:11PM +0100, Maciej W. Rozycki wrote: > It is already present in 2.4.2-ac3. Yep, I just noticed it. there was a backlog from here to tokyo. > There is a small performance impact at every interrupt -- the code that > checks for mismatches incurs it. It's just a few CPU instructions, thus > it should not be noticeable. well I saw a lot of collisions on the hub and a slow speed (approx 150kbytes sec) but I don't think collisions & patch is the cause :-) > > if you like, I can start banging the machine on it's head now. > > Please do. I believe the code is safe to be included in 2.4.3, but if > any problem is going to pop up, it'd better do it before than after > applying to the mainstream. ok, it's box killing time. I just installed a new kernel with the ptches and some additions and will reboot after I tried to kill the system. will report here. -- Grobbebol's Home | Don't give in to spammers. -o) http://www.xs4all.nl/~bengel | Use your real e-mail address /\ Linux 2.2.16 SMP 2x466MHz / 256 MB |on Usenet. _\_v - 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/
Re: apic patches (with MIS counter)
On Mon, 26 Feb 2001, Roeland Th. Jansen wrote: >CPU0 CPU1 > 0: 50644222 50826974IO-APIC-edge timer > 1: 239631 233690IO-APIC-edge keyboard > 2: 0 0 XT-PIC cascade > 3: 344151 345715IO-APIC-edge serial > 4: 4 4IO-APIC-edge serial > 5: 331569 327717IO-APIC-edge soundblaster > 8: 268433 271449IO-APIC-edge rtc > 14: 919801 913328IO-APIC-edge ide0 > 15: 22625 21407IO-APIC-edge ide1 > 18: 149973 150537 IO-APIC-level BusLogic BT-930 > 19:55575255554806 IO-APIC-level eth0 > NMI: 101420638 101425054 > LOC: 101475956 101475952 > ERR: 90 > MIS: 34865 The mismatch to IRQ count ratio looks sane. > it seems like it is time to get at least the suggestions so far in the > mainstream kernel or at least in Alan's tree. (it's not clear if it has > been already included) It is already present in 2.4.2-ac3. > There are a few things that might be related though -- some slow network > performance but I am not sure if that is caused by the patch. I don't > think so but..; I also didn't hammer the whole day on sound to crash it. There is a small performance impact at every interrupt -- the code that checks for mismatches incurs it. It's just a few CPU instructions, thus it should not be noticeable. > if you like, I can start banging the machine on it's head now. Please do. I believe the code is safe to be included in 2.4.3, but if any problem is going to pop up, it'd better do it before than after applying to the mainstream. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--+ +e-mail: [EMAIL PROTECTED], PGP key available+ - 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/
apic patches (with MIS counter)
Maciej, with the patch you sent (with MIS counter code) : CPU0 CPU1 0: 50644222 50826974IO-APIC-edge timer 1: 239631 233690IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3: 344151 345715IO-APIC-edge serial 4: 4 4IO-APIC-edge serial 5: 331569 327717IO-APIC-edge soundblaster 8: 268433 271449IO-APIC-edge rtc 14: 919801 913328IO-APIC-edge ide0 15: 22625 21407IO-APIC-edge ide1 18: 149973 150537 IO-APIC-level BusLogic BT-930 19:55575255554806 IO-APIC-level eth0 NMI: 101420638 101425054 LOC: 101475956 101475952 ERR: 90 MIS: 34865 and 11:09am up 11 days, 17:52, 8 users, load average: 1.44, 1.15, 0.77 uptime. it seems like it is time to get at least the suggestions so far in the mainstream kernel or at least in Alan's tree. (it's not clear if it has been already included) There are a few things that might be related though -- some slow network performance but I am not sure if that is caused by the patch. I don't think so but..; I also didn't hammer the whole day on sound to crash it. typically, a flood ping, sound & backup --> crash within minutes and I wanted to see how it performs (e.g. no crash) under normal loads. that part succeeded. if you like, I can start banging the machine on it's head now. -- Grobbebol's Home | Don't give in to spammers. -o) http://www.xs4all.nl/~bengel | Use your real e-mail address /\ Linux 2.2.16 SMP 2x466MHz / 256 MB |on Usenet. _\_v - 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/
apic patches (with MIS counter)
Maciej, with the patch you sent (with MIS counter code) : CPU0 CPU1 0: 50644222 50826974IO-APIC-edge timer 1: 239631 233690IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3: 344151 345715IO-APIC-edge serial 4: 4 4IO-APIC-edge serial 5: 331569 327717IO-APIC-edge soundblaster 8: 268433 271449IO-APIC-edge rtc 14: 919801 913328IO-APIC-edge ide0 15: 22625 21407IO-APIC-edge ide1 18: 149973 150537 IO-APIC-level BusLogic BT-930 19:55575255554806 IO-APIC-level eth0 NMI: 101420638 101425054 LOC: 101475956 101475952 ERR: 90 MIS: 34865 and 11:09am up 11 days, 17:52, 8 users, load average: 1.44, 1.15, 0.77 uptime. it seems like it is time to get at least the suggestions so far in the mainstream kernel or at least in Alan's tree. (it's not clear if it has been already included) There are a few things that might be related though -- some slow network performance but I am not sure if that is caused by the patch. I don't think so but..; I also didn't hammer the whole day on sound to crash it. typically, a flood ping, sound backup -- crash within minutes and I wanted to see how it performs (e.g. no crash) under normal loads. that part succeeded. if you like, I can start banging the machine on it's head now. -- Grobbebol's Home | Don't give in to spammers. -o) http://www.xs4all.nl/~bengel | Use your real e-mail address /\ Linux 2.2.16 SMP 2x466MHz / 256 MB |on Usenet. _\_v - 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/
Re: apic patches (with MIS counter)
On Mon, 26 Feb 2001, Roeland Th. Jansen wrote: CPU0 CPU1 0: 50644222 50826974IO-APIC-edge timer 1: 239631 233690IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 3: 344151 345715IO-APIC-edge serial 4: 4 4IO-APIC-edge serial 5: 331569 327717IO-APIC-edge soundblaster 8: 268433 271449IO-APIC-edge rtc 14: 919801 913328IO-APIC-edge ide0 15: 22625 21407IO-APIC-edge ide1 18: 149973 150537 IO-APIC-level BusLogic BT-930 19:55575255554806 IO-APIC-level eth0 NMI: 101420638 101425054 LOC: 101475956 101475952 ERR: 90 MIS: 34865 The mismatch to IRQ count ratio looks sane. it seems like it is time to get at least the suggestions so far in the mainstream kernel or at least in Alan's tree. (it's not clear if it has been already included) It is already present in 2.4.2-ac3. There are a few things that might be related though -- some slow network performance but I am not sure if that is caused by the patch. I don't think so but..; I also didn't hammer the whole day on sound to crash it. There is a small performance impact at every interrupt -- the code that checks for mismatches incurs it. It's just a few CPU instructions, thus it should not be noticeable. if you like, I can start banging the machine on it's head now. Please do. I believe the code is safe to be included in 2.4.3, but if any problem is going to pop up, it'd better do it before than after applying to the mainstream. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--+ +e-mail: [EMAIL PROTECTED], PGP key available+ - 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/
Re: apic patches (with MIS counter)
On Mon, Feb 26, 2001 at 01:14:11PM +0100, Maciej W. Rozycki wrote: It is already present in 2.4.2-ac3. Yep, I just noticed it. there was a backlog from here to tokyo. There is a small performance impact at every interrupt -- the code that checks for mismatches incurs it. It's just a few CPU instructions, thus it should not be noticeable. well I saw a lot of collisions on the hub and a slow speed (approx 150kbytes sec) but I don't think collisions patch is the cause :-) if you like, I can start banging the machine on it's head now. Please do. I believe the code is safe to be included in 2.4.3, but if any problem is going to pop up, it'd better do it before than after applying to the mainstream. ok, it's box killing time. I just installed a new kernel with the ptches and some additions and will reboot after I tried to kill the system. will report here. -- Grobbebol's Home | Don't give in to spammers. -o) http://www.xs4all.nl/~bengel | Use your real e-mail address /\ Linux 2.2.16 SMP 2x466MHz / 256 MB |on Usenet. _\_v - 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/
