Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Jin Guojun [VFFS]
Gary Thorpe wrote: [No subject in first one, sorry for repost] ... 1.6 Gb/s = system bus bandwidth. Cache won't affect this bandwidth. DDR400 has 400 MB/s: only attainable for long sequential accesses of either read or write but not a mix of both. DMA should be able to get near this limit (lon

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Gary Thorpe
[No subject in first one, sorry for repost] Jin Guojun [VFFS] wrote: > You are fast away from the real world. This has been explained million > times, just like > I teach intern student every summer :-) > > First of all, DDR400 and 200 MHz bus mean nothing -- A DDR 266 + 500MHz > CPU system > ca

(no subject)

2006-03-22 Thread Gary Thorpe
Jin Guojun [VFFS] wrote: > You are fast away from the real world. This has been explained million > times, just like > I teach intern student every summer :-) > > First of all, DDR400 and 200 MHz bus mean nothing -- A DDR 266 + 500MHz > CPU system > can over perform a DDR 400 + 1.7 GHz CPU syst

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Jin Guojun [VFFS]
Chris Howells wrote: On Wednesday 22 March 2006 18:52, Arne Woerner wrote: It is an ECS K7VMM or K7VMM+ if I recall it correctly... Bought in 2003... Is it easy to explain, why the 266FSB cannot do 8Gbit/sec without problem? I mean: 2*133MHz*32bit=8.3125Gbit/sec... Is the MMU too slow (e.

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Chris Howells
On Wednesday 22 March 2006 18:52, Arne Woerner wrote: > It is an ECS K7VMM or K7VMM+ if I recall it correctly... Bought in > 2003... > > Is it easy to explain, why the 266FSB cannot do 8Gbit/sec without > problem? I mean: 2*133MHz*32bit=8.3125Gbit/sec... Is the MMU too > slow (e. g. due to "cheap"

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Jin Guojun [VFFS]
Arne Woerner wrote: Notice that your memory copy speed will be one half of it. Why "half"? dd causes two copies but counts each byte just once... Maybe "dd" in combination with /dev/zero is not the right way to measure memory bandwidth? It depends on how /dev/null implemented. It m

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Jin Guojun [VFFS]
Arne Woerner wrote: It depends on how you use /dev/zero. dd of=/dev/null if=/dev/zero bs=4k count=100k tests cache speed % dd of=/dev/null if=/dev/zero bs=4k count=100k 102400+0 records in 102400+0 records out 419430400 bytes transferred in 0.204511 secs (2050894814 bytes/sec) ab

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Jin Guojun [VFFS]
Arne Woerner wrote: --- "Jin Guojun [VFFS]" [1]<[EMAIL PROTECTED]> wrote: In you example: Now your 1.6 GB/s reduced to 16MB/s or even worse just based on this factor. What did we show by this <> test? I thought that would prove the memory bandwidth is about 8Gbit/sec (1GByte/sec; 2 * /2^3

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Arne Woerner
--- "Jin Guojun [VFFS]" <[EMAIL PROTECTED]> wrote: > Even after your program finished, you had only 277 MB/s (DDR memory?), > which is far below a good motherboard. Good motherboards should > have 500 - 900 MB/s memory bandwidth, while expensive motherboards > can have 1-3 GB/s memory bandwidth, wh

Re: packet drop with intel gigabit / marwell gigabit

2006-03-22 Thread Arne Woerner
--- "Jin Guojun [VFFS]" <[EMAIL PROTECTED]> wrote: >Arne Woerner wrote: >> What did we show by this <> test? I thoughtthat >> would prove the memory bandwidth is about 8Gbit/sec(1GByte/sec; >> 2 * >number>/2^30). >> > It depends on how you use /dev/zero. > dd of=/dev/null if=/dev/zero bs=4k cou