netdev
[Top] [All Lists]

Re: netlink drops messages.

To: kuznet@xxxxxxxxxxxxx
Subject: Re: netlink drops messages.
From: "James R. Leu" <jleu@xxxxxxxxxxxxxx>
Date: Tue, 16 Jan 2001 12:43:19 -0600
Cc: jleu@xxxxxxxxxxxxxx, gleb@xxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <200101161832.VAA31543@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Tue, Jan 16, 2001 at 09:32:24PM +0300
Organization: none
References: <20010116121252.B1299@doit.wisc.edu> <200101161832.VAA31543@ms2.inr.ac.ru>
Reply-to: jleu@xxxxxxxxxxxxxx
Sender: owner-netdev@xxxxxxxxxxx
On Tue, Jan 16, 2001 at 09:32:24PM +0300, kuznet@xxxxxxxxxxxxx wrote:
> Hello!
> 
> > Are you saying that an application should not rely on netlink to deliver
> > accurate and complete information about interface or routing changes?
> > AND that re-reading the entire route table or interface table is the correct
> > solution to this problem?
> 
> "Reliable" delivery without retransmissions is possible provided
> you have infinite amount of memory. 8)8)8)
> 
> You never have and ENOBUFS provides necessary retransmission logic.

You didn't say "retransmission" of missed netlink information, you said
"resynchronize doing dumps".  These are completly differnt things.

If netlink can't provide reliable update information then it needs to be
changed.  How is it that we can provide reliable transport of information
across the internet via TCP, yet a netlink socket within the same box
cannot?

Jim

> Alexey

-- 
James R. Leu

<Prev in Thread] Current Thread [Next in Thread>