From: "Julius Volz" <juliusv@google.com>
To: netdev@vger.kernel.org
Cc: "Patrick McHardy" <kaber@trash.net>,
"Vince Busam" <vbusam@google.com>, "Thomas Graf" <tgraf@suug.ch>
Subject: Sending big Netlink messages to userspace
Date: Tue, 24 Jun 2008 18:38:07 +0200 [thread overview]
Message-ID: <f4845fc0806240938h36d275ect109fd5f5414cba37@mail.gmail.com> (raw)
Hi,
While adding a Netlink interface to IPVS, I've been wondering how to
properly send very big messages to userspace and found these posts:
http://lists.openwall.net/netdev/2007/03/06/214
http://lists.openwall.net/netdev/2007/03/07/2
Herbert writes in the second one, "Dumps should be done using 4K
(NLMSG_GOODSIZE) skb's, where is the problem?" How is that meant?
Should one manually split up dumps into several NLMSG_GOODSIZE
messages or is there some mechanism for that?
I need to send arbitrarily long lists to userspace and I'm already
choosing a big enough size for nlmsg_new(), so I get no put failures
while constructing the message. However, when receiving the data in
userspace (with libnl), the receive callback is never called. An
strace shows that MSG_TRUNC is set in the oversized message, so the
data is never fully received.
I just call nl_recvmsgs_default(sock) once (which does not return an
error). Am I handling libnl incorrectly or do I need to do this
differently on the kernel side?
Thanks,
Julius
--
Google Switzerland GmbH
next reply other threads:[~2008-06-24 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 16:38 Julius Volz [this message]
2008-06-24 17:00 ` Sending big Netlink messages to userspace Patrick McHardy
2008-06-24 18:18 ` Julius Volz
2008-06-25 10:44 ` Thomas Graf
2008-06-25 18:56 ` Julius Volz
2008-06-26 10:01 ` Thomas Graf
2008-06-25 22:51 ` David Miller
2008-06-26 0:41 ` Patrick McHardy
2008-06-26 15:39 ` Julius Volz
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=f4845fc0806240938h36d275ect109fd5f5414cba37@mail.gmail.com \
--to=juliusv@google.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=vbusam@google.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).