From: Patrick McHardy <kaber@trash.net>
To: Chris Friesen <cfriesen@nortel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: question on netlink_overrun()
Date: Thu, 05 Mar 2009 06:56:02 +0100 [thread overview]
Message-ID: <49AF6972.8000103@trash.net> (raw)
In-Reply-To: <49AF2871.10804@nortel.com>
Chris Friesen wrote:
> Currently we set netlink_overrun() on the socket in both the unicast and
> broadcast paths. If I understand things correctly this should result in
> the receiver getting ENOBUFS the next time they try a socket-related
> syscall.
>
> However, in the netlink_dump() code we don't call it--was this an
> oversight or an intentional design decision?
>
> I have a userspace app that would like to know if it ran out of buffer
> space in the receive socket (and hence lost some packets) while dumping
> SA information in xfrm_user_rcv_msg().
The dump should never overrun since it has flow control based
on available socket memory. Once the decision has been made
to send a dump packet and it has been sucessfully allocated,
it is never dropped. Except when explicitly filtered.
prev parent reply other threads:[~2009-03-05 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 1:18 question on netlink_overrun() Chris Friesen
2009-03-05 5:56 ` Patrick McHardy [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=49AF6972.8000103@trash.net \
--to=kaber@trash.net \
--cc=cfriesen@nortel.com \
--cc=davem@davemloft.net \
--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).