On Thu, Jul 26, Stefan Laudat wrote: > Identical network cards for Win2k, Linux SMP and OpemBSD processor (Intel > Pro 100). Linux was run on dual p3/1Ghz(SMP), Pentium2/400Mhz and P3/800Mhz > (UP). Windows 2000 was run on p3/1Ghz UP. I've made tests with same results > against Linux UP boxes running on Celeron/600 with 3com Vortex and realtek > 8139 NICs. I've outlined that the result is the same no matter if you hit > via 1Gbit or 100Mbit. Could you test the pro100 adapter with the intel e100 driver with cpu-saver enabled (insmod e100.o ucode=1) ? (Also playing around with other parameters like IntDelay, BundleMax and Tx/RxDescriptors might make a difference). The 'cpu-saver' option should limit the number of interrupts the nic generates (this might help if the interrupts bring the machine to halt) (read the e100 driver manual for more information). -Jarno -- Jarno Huuskonen <[EMAIL PROTECTED]>
- Re: UDP packet handling weird behaviour of vario... Stefan Laudat
- Re: UDP packet handling weird behaviour of v... Niels Bakker
- RE: UDP packet handling weird behaviour of vario... David LeBlanc
- Re: UDP packet handling weird behaviour of vario... Radu-Adrian Feurdean
- Re: UDP packet handling weird behaviour of various op... trop
- Re: UDP packet handling weird behaviour of various op... Paul Sack
- Re: UDP packet handling weird behaviour of vario... Stefan Laudat
- Re: UDP packet handling weird behaviour of v... Sean Hunter
- Re: UDP packet handling weird behaviour ... Sean Hunter
- Re: UDP packet handling weird behaviour of v... Adrian Chadd
- solaris in.lpd patch where/when? Jarno Huuskonen
- solaris in.lpd patch where/when? Jake Luck
- Re: UDP packet handling weird behaviour of various op... Juergen P. Meier
- Re: UDP packet handling weird behaviour of various op... Pavlos Parissis
- RE: UDP packet handling weird behaviour of various op... Boyan Krosnov
