From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: iproute uses too small of a receive buffer
Date: Tue, 27 Oct 2009 16:16:52 -0700 [thread overview]
Message-ID: <4AE77F64.3090302@candelatech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
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@i7-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@candelatech.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
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
[-- Attachment #2: iputils.patch --]
[-- Type: text/plain, Size: 343 bytes --]
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));
next reply other threads:[~2009-10-27 23:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 23:16 Ben Greear [this message]
2009-10-27 23:24 ` iproute uses too small of a receive buffer Stephen Hemminger
2009-10-27 23:30 ` Ben Greear
2009-10-28 7:01 ` Eric Dumazet
2009-10-28 7:09 ` Eric Dumazet
2009-10-28 7:37 ` Eric Dumazet
2009-10-28 7:52 ` Eric Dumazet
2009-10-28 7:55 ` David Miller
2009-10-28 19:05 ` Patrick McHardy
2009-10-28 19:19 ` Ben Greear
2009-10-28 19:50 ` Patrick McHardy
2009-10-28 20:04 ` Ben Greear
2009-10-28 20:07 ` Patrick McHardy
2009-10-28 20:21 ` Ben Greear
2009-11-10 17:15 ` Stephen Hemminger
2009-10-28 20:38 ` Eric Dumazet
2009-10-29 8:17 ` David Miller
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=4AE77F64.3090302@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/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).