[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091027162434.6dc31b2d@nehalam>
Date: Tue, 27 Oct 2009 16:24:34 -0700
From: Stephen Hemminger <shemminger@...tta.com>
To: Ben Greear <greearb@...delatech.com>
Cc: NetDev <netdev@...r.kernel.org>
Subject: Re: iproute uses too small of a receive buffer
On Tue, 27 Oct 2009 16:16:52 -0700
Ben Greear <greearb@...delatech.com> wrote:
> I have a very busy system with a bunch of xorp router processes (mis)configured.
>
> This thing is rapidly making route changes for whatever reason.
>
> The 'ip monitor route' command was failing:
>
> [root@...dqc-1 ]# ip monitor route
> netlink receive error No buffer space available (105)
> Dump terminated
>
>
> It is only using a 32k rcv buffer, and it seems the OS was
> overdriving it.
>
> Please consider making the rcv buffer larger, perhaps something
> like this (inline is white-space damaged...attachment should apply
> if deemed useful.):
>
> Signed-off-by: Ben Greear <greearb@...delatech.com>
>
> diff --git a/lib/libnetlink.c b/lib/libnetlink.c
> index b68e2fd..95a7d1d 100644
> --- a/lib/libnetlink.c
> +++ b/lib/libnetlink.c
> @@ -38,7 +38,7 @@ int rtnl_open_byproto(struct rtnl_handle *rth, unsigned subscriptions,
> {
> socklen_t addr_len;
> int sndbuf = 32768;
> - int rcvbuf = 32768;
> + int rcvbuf = 3276800;
>
> memset(rth, 0, sizeof(*rth));
>
>
> Thanks,
> Ben
>
Just having larger buffer isn't guarantee of success. Allocating
a huge buffer is not going to work on embedded.
Why not have it continue after one error.
--
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists