Skip to contentSkip to conversation

Performance is weird (fwd)

DISCUSSION Manfred Spraul 2 participants 4 messages Mar 15, 2001 – Mar 17, 2001

lore
Share & tools
lore
#0 lore raw

I've attached a patch.
I tried to trigger the problem with my 10 MBit ne2k-pci connection, but without success.

Could you try it?
I've tested it with -ac17, and it applies to 2.4.2 cleanly.

--
Manfred

arch/i386/kernel/process.c +5 -0
@@ -81,6 +81,11 @@
 {
 	if (current_cpu_data.hlt_works_ok && !hlt_counter) {
 		__cli();
+		if (softirq_active(smp_processor_id()) & softirq_mask(smp_processor_id())) {
+			__sti();
+			do_softirq();
+			return;
+		}
 		if (!current->need_resched)
 			safe_halt();
 		else
#1 lore raw

Re: Performance is weird (fwd) -> results

Quoted 6 lines · Manfred Spraul

I've attached a patch.
I tried to trigger the problem with my 10 MBit ne2k-pci connection, but without success.

Could you try it?
I've tested it with -ac17, and it applies to 2.4.2 cleanly.

On 2.4.2:

Before:
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 atm -> 0.90
ttcp-t: socket
ttcp-t: 16777216 bytes in 3.829257 real seconds = 4278.636822 KB/sec (35.050593 Mb/sec)

After either of your patches, the result was the same, sorry.

I tried to apply the patch to 2.4.3 and still got the better result with it, altought compiling kernel still improved the performance.

First:

[root@ropogw test]# ./ttcp_atm -t -a -s 0.90
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 atm -> 0.90
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.994121 real seconds = 8216.151377 KB/sec (67.306712 Mb/sec)
[root@ropogw test]# ./ttcp_atm -t -a -s 0.90
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 atm -> 0.90
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.995773 real seconds = 8209.350462 KB/sec (67.250999 Mb/sec)
[root@ropogw test]# ./ttcp_atm -t -a -s 0.90
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 atm -> 0.90
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.989680 real seconds = 8234.489968 KB/sec (67.456942 Mb/sec)

(start to compile kernel on other console)

[root@ropogw test]# ./ttcp_atm -t -a -s 0.90
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 atm -> 0.90
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.072744 real seconds = 15272.982184 KB/sec (125.116270 Mb/sec)
[root@ropogw test]# ./ttcp_atm -t -a -s 0.90
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 atm -> 0.90
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.140261 real seconds = 14368.640162 KB/sec (117.70790

I also applied it the test to the 3com card:

Before kernel compiling, patch applied or not:

ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 udp -> not.for.your.eyes
ttcp-t: socket
ttcp-t: 16777216 bytes in 2.218013 real seconds = 7386.791691 KB/sec (60.512598 Mb/sec)

ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5013 udp -> not.for.your.eyes
ttcp-t: socket
ttcp-t: 16777216 bytes in 1.428264 real seconds = 11471.268617 KB/sec (93.972633 Mb/sec)

Thanks,

Sampsa Ranta
[email protected]

#2 lore raw

Re: Performance is weird (fwd) -> results

Quoted 3 lines · Sampsa Ranta

After either of your patches, the result was the same, sorry.

Is apm or acpi running?

--
Manfred

#3 lore raw

Re: Performance is weird (fwd) -> results

Quoted 5 lines · Manfred Spraul
Quoted 3 lines · Sampsa Ranta

After either of your patches, the result was the same, sorry.

Is apm or acpi running?

No, I tried both SMP and non-SMP version of kernel, the machine is however single processor Athlon 900. CONFIG_ACPI is not set, CONFIG_APM is not set. The 2.4.3pre4 still performs 66M/s without "the load" and 124M/s+ with load. However there is much different between 2.4.2 and 2.4.3pre about 33M/s to 66M/s.

- Sampsa Ranta
[email protected]