| To: | Simon Kirby <sim@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Route cache performance under stress |
| From: | Jamal Hadi <hadi@xxxxxxxxxxxxxxxx> |
| Date: | Tue, 10 Jun 2003 07:28:16 -0400 (EDT) |
| Cc: | ralph+d@xxxxxxxxx, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>, "linux-net@xxxxxxxxxxxxxxx" <linux-net@xxxxxxxxxxxxxxx> |
| In-reply-to: | <20030610043453.GC23009@netnation.com> |
| References: | <008001c32eda$56760830$4a00000a@badass> <20030609195652.E35696@shell.cyberus.ca> <Pine.LNX.4.51.0306092006420.12038@ns.istop.com> <20030609204257.L35799@shell.cyberus.ca> <Pine.LNX.4.51.0306092200150.28167@ns.istop.com> <20030610043453.GC23009@netnation.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Mon, 9 Jun 2003, Simon Kirby wrote: > I was going to ask before, and it's probably not even possible anymore, > but have you tried on a 2.0 kernel before? 2.0 kernels probably have a > lot of other problems and don't support the new hardware, but it would be > interesting to see how it scales to many srcs/dsts before the route cache > was integrated. It probably scales a lot more like FreeBSD does. You'd > probably have to use eepro100s or something, though. > As a side note, note that stateless forwarding like BSD patricie tries is no longer sufficient. Its no longer just looking up a nexthop, dec ttl, recompute csum that we are optimizing for. The dst cache/flowi is the way to go, so theres no going back;-> - we just gotta make what we have work better. cheers, jamal |
| Previous by Date: | Re: Route cache performance tests, Jamal Hadi |
|---|---|
| Next by Date: | RE: Route cache performance under stress, Pekka Savola |
| Previous by Thread: | Re: Route cache performance under stress, Jamal Hadi |
| Next by Thread: | Re: Route cache performance under stress, Ralph Doncaster |
| Indexes: | [Date] [Thread] [Top] [All Lists] |