netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net (David Miller), netdev@vger.kernel.org
Subject: Re: netlink recvmsg() and MSG_TRUNC
Date: Tue, 6 Mar 2007 15:57:50 -0800	[thread overview]
Message-ID: <20070306155750.7827ab1d@freekitty> (raw)
In-Reply-To: <E1HOjP1-0003NM-00@gondolin.me.apana.org.au>

On Wed, 07 Mar 2007 10:49:07 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> David Miller <davem@davemloft.net> wrote:
> > 
> > I guess one thing the user could do when it sees MSG_TRUNC
> > is keep calling recvmsg() until the receive queue is emptied
> > of packets, in order to get that pesky nlk->cb cleared to
> > NULL, then resubmit.
> > 
> > But that's rediculous and complicated.
> > 
> > Any ideas?
> 
> Which netlink family generates (or needs to generate) unbounded
> messages to user-space? Or indeed which ones generate messages
> greater than 64K (or 4K for that matter)?
> 
> Cheers,

I know some commands send big blocks down of configuration information.
One example is netem statistical data, but there are others.

-- 
Stephen Hemminger <shemminger@linux-foundation.org>

  reply	other threads:[~2007-03-06 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 23:19 netlink recvmsg() and MSG_TRUNC David Miller
2007-03-06 23:40 ` James Morris
2007-03-06 23:49 ` Herbert Xu
2007-03-06 23:57   ` Stephen Hemminger [this message]
2007-03-07  0:04     ` Herbert Xu
2007-03-07  0:02   ` David Miller
2007-03-07  0:04     ` Herbert Xu
2007-03-07  0:05       ` David Miller
2007-03-07  0:07         ` Herbert Xu

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=20070306155750.7827ab1d@freekitty \
    --to=shemminger@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --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).