All of lore.kernel.org
 help / color / mirror / Atom feed
From: roopa <roopa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: aderumier@odiso.com, ronen.arad@intel.com,
	netdev@vger.kernel.org, rami.rosen@intel.com
Subject: Re: [pve-devel] bridge vlan range, kernel 4.1 : "message truncated" warning when too much vlans defined
Date: Thu, 10 Sep 2015 17:02:51 -0700	[thread overview]
Message-ID: <55F21A2B.6070205@cumulusnetworks.com> (raw)
In-Reply-To: <20150910.155830.1391952981935838143.davem@davemloft.net>

On 9/10/15, 3:58 PM, David Miller wrote:
> From: roopa <roopa@cumulusnetworks.com>
> Date: Thu, 10 Sep 2015 15:26:30 -0700
>
>> On 9/9/15, 11:40 PM, Alexandre DERUMIER wrote:
>>> Hi,
>>>
>>> This still not fixed in iproute 4.2.
>>>
>>> Is they any plan to increase the rtnl_dump_filter buffer size soon ?
>> Instead of increasing the default size, it would be nicer if this was
>> configurable for iproute2 (I haven't looked yet).
> I would definitely prefer this be done in a run-time manner of some
> sort, and then other libraries can use iproute2's logic as a reference
> for how to deal with this reliably, properly, and in a %100
> future-proof manner.
>
> Something of the "if request X fails, double the buffer size" variety.
agreed. This would be ideal. libnl already handles it this way.
We have to move iproute2 recv buffer to dynamic allocation and also 
realloc on MSG_TRUNC.

I can get to it one of these days unless somebody beats me to it.

thanks.

      reply	other threads:[~2015-09-11  0:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 18:24 bridge vlan range, kernel 4.1 : "message truncated" warning when too much vlans defined Alexandre DERUMIER
2015-07-30  2:03 ` Arad, Ronen
2015-07-30  5:31   ` Alexandre DERUMIER
2015-09-10  6:40     ` [pve-devel] " Alexandre DERUMIER
2015-09-10 22:26       ` roopa
2015-09-10 22:58         ` David Miller
2015-09-11  0:02           ` roopa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55F21A2B.6070205@cumulusnetworks.com \
    --to=roopa@cumulusnetworks.com \
    --cc=aderumier@odiso.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=rami.rosen@intel.com \
    --cc=ronen.arad@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.