| To: | Andi Kleen <ak@xxxxxx> |
|---|---|
| Subject: | Re: netlink drops messages. |
| From: | "Benjamin C.R. LaHaise" <blah@xxxxxxxxx> |
| Date: | Thu, 18 Jan 2001 16:31:41 -0500 (EST) |
| Cc: | jamal <hadi@xxxxxxxxxx>, Werner Almesberger <Werner.Almesberger@xxxxxxx>, "James R. Leu" <jleu@xxxxxxxxxxxxxx>, kuznet@xxxxxxxxxxxxx, gleb@xxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20010118152452.A5289@fred.local> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Thu, 18 Jan 2001, Andi Kleen wrote: > On Thu, Jan 18, 2001 at 01:47:04PM +0100, jamal wrote: > > 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. > > It is when you go to "dump netlink state every 60s" mode on overload. Arguing about |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: internal drops with tcp, kernel 2.2.16, Andi Kleen |
|---|---|
| Next by Date: | Re: netlink drops messages., Benjamin C.R. LaHaise |
| Previous by Thread: | Re: netlink drops messages., Andi Kleen |
| Next by Thread: | Re: netlink drops messages., Benjamin C.R. LaHaise |
| Indexes: | [Date] [Thread] [Top] [All Lists] |