netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: roopa@cumulusnetworks.com
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 15:58:30 -0700 (PDT)	[thread overview]
Message-ID: <20150910.155830.1391952981935838143.davem@davemloft.net> (raw)
In-Reply-To: <55F20396.9090505@cumulusnetworks.com>

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.

  reply	other threads:[~2015-09-10 22:58 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 [this message]
2015-09-11  0:02           ` roopa

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=20150910.155830.1391952981935838143.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=aderumier@odiso.com \
    --cc=netdev@vger.kernel.org \
    --cc=rami.rosen@intel.com \
    --cc=ronen.arad@intel.com \
    --cc=roopa@cumulusnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).