This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] IPv6 on P2P links
- Previous message (by thread): [ipv6-wg] IPv6 on P2P links
- Next message (by thread): [ipv6-wg] IPv6 on P2P links
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniele Orlandi
daniele at orlandi.com
Thu May 26 18:33:42 CEST 2011
On Thursday 26 May 2011 10:07:39 Jasper Jans wrote: > Can anyone give me some real world experience with IPv6 numbering on P2P > links in their network? I've not yet been able to figure out another aspect of prefixes longer than /64. How are TCAMs in hardware routers and routing lookup code going to handle matches longer than 64 bits? Are ALL vendors putting all the 128 bits in the TCAMs or is there someone (or most?) with reduced match size that implies a second lookup? Or is the CPU-based algorithm going to be slower if the match is greater than the native CPU word size? That, alone would justify avoiding having prefixes longer than a /64 in the FIB since it would mean reduced PPS throughput for those destinations. Is anyone with an insight view of actual lookup method able to enlighten me a bit? Bye, -- Daniele "Vihai" Orlandi Bieco Illuminista #184213
- Previous message (by thread): [ipv6-wg] IPv6 on P2P links
- Next message (by thread): [ipv6-wg] IPv6 on P2P links
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]