Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Queue\s+and\s+SMP\s+locking\s+discussion\s+$was\s+Re\:\s+3c59x\.c$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Queue\s+and\s+SMP\s+locking\s+discussion\s+$was\s+Re\:\s+3c59x\.c$\s*$/: 42 ]

Total 42 documents matching your query.

41. Re: Queue and SMP locking discussion (was Re: 3c59x.c) (score: 1): Author: Michael Richardson <mcr@xxxxxxxxxxx>; Date: Fri, 31 Mar 2000 14:08:19 -0500; kuznet> Khm... Please, get some simple benchmark applet sort of netperf kuznet> and enjoy with this impossible phenomenon on single 100Mbit kuznet> interface. Despite of all the "max job on interrup; /archives/netdev/2000-03/msg00167.html (11,085 bytes)
42. Re: Queue and SMP locking discussion (was Re: 3c59x.c) (score: 1): Author: Andrey Savochkin <saw@xxxxxxxxxxxxx>; Date: Sat, 1 Apr 2000 11:30:10 +0800; Hello, At least for eepro100, the receive interrupt mitigation doesn't exist in the driver. There were some changes about TX completion interrupts, but I consider them as rather irrelevant. The other; /archives/netdev/2000-03/msg00168.html (10,890 bytes)

Current List: 41 - 42
Page: [1] [2] [3]