From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
NetDev <netdev@vger.kernel.org>
Subject: Re: iproute uses too small of a receive buffer
Date: Wed, 28 Oct 2009 08:01:57 +0100 [thread overview]
Message-ID: <4AE7EC65.8000600@gmail.com> (raw)
In-Reply-To: <4AE78297.9000909@candelatech.com>
Ben Greear a écrit :
>
> Probably the right way is to give a cmd-line arg to set the buffer size
> and also continue if the error is ENOBUFs (but print some error out
> so users know they have issues). I can make the attempt if that
> sounds good to you.
Real fix is to realloc buffer at receive time, no need for user setting.
In my testings I saw it reaching 1 Mbyte
write(2, "REALLOC buflen 8192\n"..., 20) = 20
write(2, "REALLOC buflen 16384\n"..., 21) = 21
write(2, "REALLOC buflen 32768\n"..., 21) = 21
write(2, "REALLOC buflen 65536\n"..., 21) = 21
write(2, "REALLOC buflen 131072\n"..., 22) = 22
write(2, "REALLOC buflen 262144\n"..., 22) = 22
write(2, "REALLOC buflen 524288\n"..., 22) = 22
[iproute2] realloc buffer in rtnl_listen
# ip monitor route
netlink receive error No buffer space available (105)
Dump terminated
Reported-by: Ben Greear<greearb@candelatech.com>
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
diff --git a/lib/libnetlink.c b/lib/libnetlink.c
index b68e2fd..134ce7f 100644
--- a/lib/libnetlink.c
+++ b/lib/libnetlink.c
@@ -392,8 +392,14 @@ int rtnl_listen(struct rtnl_handle *rtnl,
.msg_iov = &iov,
.msg_iovlen = 1,
};
- char buf[8192];
+ char *buf;
+ size_t buflen = 8192;
+ buf = malloc(buflen);
+ if (buf == NULL) {
+ fprintf(stderr, "netlink could not alloc %lu bytes\n", buflen);
+ return -1;
+ }
memset(&nladdr, 0, sizeof(nladdr));
nladdr.nl_family = AF_NETLINK;
nladdr.nl_pid = 0;
@@ -401,12 +407,20 @@ int rtnl_listen(struct rtnl_handle *rtnl,
iov.iov_base = buf;
while (1) {
- iov.iov_len = sizeof(buf);
+ iov.iov_len = buflen;
status = recvmsg(rtnl->fd, &msg, 0);
if (status < 0) {
if (errno == EINTR || errno == EAGAIN)
continue;
+ if (errno == ENOBUFS) {
+ buf = realloc(buf, buflen * 2);
+ if (buf) {
+ buflen *= 2;
+ iov.iov_base = buf;
+ continue;
+ }
+ }
fprintf(stderr, "netlink receive error %s (%d)\n",
strerror(errno), errno);
return -1;
next prev parent reply other threads:[~2009-10-28 7:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 23:16 iproute uses too small of a receive buffer Ben Greear
2009-10-27 23:24 ` Stephen Hemminger
2009-10-27 23:30 ` Ben Greear
2009-10-28 7:01 ` Eric Dumazet [this message]
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=4AE7EC65.8000600@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).