| To: | Andi Kleen <ak@xxxxxx> |
|---|---|
| Subject: | Re: netlink drops messages. |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Thu, 18 Jan 2001 07:46:14 -0500 (EST) |
| Cc: | Werner Almesberger <Werner.Almesberger@xxxxxxx>, "James R. Leu" <jleu@xxxxxxxxxxxxxx>, <kuznet@xxxxxxxxxxxxx>, <gleb@xxxxxxxxxxx>, <netdev@xxxxxxxxxxx> |
| In-reply-to: | <20010118125936.B3272@xxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Thu, 18 Jan 2001, Andi Kleen wrote: > I suspect if someone is really seriously expecting to handle hundreds of > interface up/down per seconds they would opt for shared memory. For routes > you do not even need kernel support, because you can do that privately with > the routing daemon. Sounds nice. I think hundreds of interface up/down per seconds is extreme end unless you have "dynamic" type of devices like L2TP which come and go (lets not go into the interface discussion again ;-<). Having said that, the router has to be robust to hundreds of interface up/down per seconds. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: internal drops with tcp, kernel 2.2.16, Chris Wedgwood |
|---|---|
| Next by Date: | Re: internal drops with tcp, kernel 2.2.16, jamal |
| Previous by Thread: | Re: netlink drops messages., Chris Wedgwood |
| Next by Thread: | Re: netlink drops messages., Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |