| To: | kuznet@xxxxxxxxxxxxx |
|---|---|
| Subject: | Re: netlink drops messages. |
| From: | "James R. Leu" <jleu@xxxxxxxxxxxxxx> |
| Date: | Tue, 16 Jan 2001 13:14:56 -0600 |
| Cc: | jleu@xxxxxxxxxxxxxx, gleb@xxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200101161848.VAA31729@xxxxxxxxxxxxx>; from kuznet@xxxxxxxxxxxxx on Tue, Jan 16, 2001 at 09:48:48PM +0300 |
| Organization: | none |
| References: | <20010116124319.D1299@xxxxxxxxxxxxx> <200101161848.VAA31729@xxxxxxxxxxxxx> |
| Reply-to: | jleu@xxxxxxxxxxxxxx |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Tue, Jan 16, 2001 at 09:48:48PM +0300, kuznet@xxxxxxxxxxxxx wrote: > Hello! > > > You didn't say "retransmission" of missed netlink information, you said > > "resynchronize doing dumps". These are completly differnt things. > > Think a bit. About what? How silly it is to think that netlink isn't reliable? > > If netlink can't provide reliable update information then it needs to be > > changed. > > 8)8)8) > > If you will invent a way to reliably store N bytes having > storage of only 1 byte, you will make a revolution in technique. 8) I'm not asking for the impossible. Sequence numbers and/or client to server ACKs would solve the problem. Jim > Alexey -- James R. Leu |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: netlink drops messages., kuznet |
|---|---|
| Next by Date: | Re: netlink drops messages., kuznet |
| Previous by Thread: | Re: netlink drops messages., kuznet |
| Next by Thread: | Re: netlink drops messages., kuznet |
| Indexes: | [Date] [Thread] [Top] [All Lists] |