[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Masataka Ohta
mohta at necom830.hpcl.titech.ac.jp
Wed May 10 10:53:36 CEST 2006
Oliver Bartels wrote: >>I'm saying that, given a so short duration for routing table lookup, >>we must make memory for routing table smaller and simpler. Note that, >>at 1Tbps, 500B packet is 4ns long, at 10Tbps 0.4ns. > Have you ever heared of multi stage lookup using _pipelining_ ? Yes, of course. Sometimes, pipelining can improve performance by a small constant factor with a small amount of additional hardware. > If yes, you should be able to understand why your problem > isn't a problem at all. Pipelining requires pipeline resigters. If you have too much stages of pipelining, additional amount of pipeline registers kills the benefit. Masataka Ohta
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]