"Miquel van Smoorenburg" <[email protected]> writes: > And > if you need to route more than say 3 gbit/s, PC hardware just > won't cut it. Each new x86 hardware generation normally can route more than the previous generation. If you give out such a dubious number you would always need to give it a (short) expiry date. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Routing 600+ vlan's via linux problems (looks like arp problems)
- From: "Øyvind Vågen Jægtnes" <[email protected]>
- Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- From: Willy Tarreau <[email protected]>
- Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- From: Jan Engelhardt <[email protected]>
- Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- From: "Øyvind Vågen Jægtnes" <[email protected]>
- Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- From: Willy Tarreau <[email protected]>
- Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- From: "Miquel van Smoorenburg" <[email protected]>
- Routing 600+ vlan's via linux problems (looks like arp problems)
- Prev by Date: Re: [PATCH 1/5] fallocate() implementation in i86, x86_64 and powerpc
- Next by Date: Re: swap-prefetch: 2.6.22 -mm merge plans
- Previous by thread: Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- Next by thread: Re: Routing 600+ vlan's via linux problems (looks like arp problems)
- Index(es):
 |