[Xorp-hackers] XORP IPC mechanism is stressed by data plane traffic

Bruce M Simpson bms@spc.org
Thu, 24 Mar 2005 12:16:45 -0800


On Thu, Mar 24, 2005 at 10:08:45PM +0800, edrt wrote:
> >If you don't increase the XORP tasks' priority does it still work?
> >Also, if you add ENOBUFS to is_pseudo_error without increasing the
> >network mbuf does it still work?
> 
>  * With low priority XORP tasks, call_xrl will be very slow, read failed
>    with multiple EWOULDBLOCK until eventually call_xrl timeout.
>  * With high priority XORP tasks, low mbuf, ignore ENOBUFS in is_pseudo_error, 
>    all XORP components complains ENOBUFS when they communicate.

Which version of FreeBSD are you running?

Can you grab the output of netstat -m when this happens (are you running
out of packet headers, or clusters) ?

Is sysctl net.inet.tcp.do_tcpdrain enabled?

What is the tunable kern.ipc.nmbclusters set to?

Can you provide any metrics about how much traffic you are dealing
with (and how much of it is multicast) when this happens?

BMS