[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160304153553.47e8741d@xeon-e3>
Date: Fri, 4 Mar 2016 15:35:53 -0800
From: Stephen Hemminger <shemming@...cade.com>
To: Phil Sutter <phil@....cc>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [iproute PATCH] libnetlink: Double the dump buffer size
On Fri, 4 Mar 2016 18:57:28 +0000
Phil Sutter <phil@....cc> wrote:
> There have been reports about 'ip addr' printing "Message truncated" on
> systems with large numbers of VFs. Although I haven't been able to get
> my hands on hardware suitable to reproduce this, increasing the dump
> buffer has been reported to resolve the issue. For want of a better
> idea, just double the buffer size to 32k.
>
> Feels like this opportunistic buffer size selection is rather
> workarounding a design flaw in libnetlink or maybe even the netlink
> protocol itself.
>
> Signed-off-by: Phil Sutter <phil@....cc>
> ---
> lib/libnetlink.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/libnetlink.c b/lib/libnetlink.c
> index d6b5fd3e8a493..245c4ca216753 100644
> --- a/lib/libnetlink.c
> +++ b/lib/libnetlink.c
> @@ -223,7 +223,7 @@ int rtnl_dump_filter_l(struct rtnl_handle *rth,
> .msg_iov = &iov,
> .msg_iovlen = 1,
> };
> - char buf[16384];
> + char buf[32768];
> int dump_intr = 0;
>
> iov.iov_base = buf;
I thought this was addressed in kernel by making the VF info optional.
The netlink protocol is showing some strain, this is one of them.
Powered by blists - more mailing lists