Messages in this thread | | | Date | Wed, 16 Jan 2002 09:33:48 -0800 | From | "Amit Gupta" <> | Subject | Re: arpd not working in 2.4.17 or 2.5.1 |
| |
We do have more than 1024 systems dircetly connected using switches.. and I am working on getting a "lsf linux server master", which requires to open connections all the machines in almost every second or so. Everthing works fine but as soon as the master daemon tries to connect to systems >1024.. arp kills it with
Jan 15 08:54:08 lx-master kernel: NET: 464 messages suppressed. Jan 15 08:54:08 lx-master kernel: Neighbour table overflow. Jan 15 08:54:08 lx-master last message repeated 9 times Jan 15 08:54:54 lx-master kernel: NET: 442 messages suppressed. Jan 15 08:54:54 lx-master kernel: Neighbour table overflow. Jan 15 08:54:54 lx-master last message repeated 8 times Jan 15 08:56:24 lx-master kernel: NET: 443 messages suppressed. Jan 15 08:56:24 lx-master kernel: Neighbour table overflow.
-Amit
Luigi Genoni wrote:
> On Tue, 15 Jan 2002, Alan Cox wrote: > > > > But arp>1024 is Very Important, else linux will never be able to talk to more > > > than 1024 clients ! > > > > > > Linux is my favourite and I wonder if this limit will kill linux for the race > > > with Solaris/M$ server market. So pls save me :) and help neighour.c/network > > > layer in new kernel. > > > > ARP applies for local links only. So you need a network you are actively > > talking to 1024 different hosts directly on. Furthermore all the > > config items should now be soft anyway. Want more, enable more. > > To have this kind of network is not impossible at all, I received mail > from people at intel who are dealing with around 5000 arp (they say). > In this situation with arpd there was no sensible performance loss, right > now there is a big slowdown.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |