| To: | jleu@xxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: netlink drops messages. |
| From: | kuznet@xxxxxxxxxxxxx |
| Date: | Tue, 16 Jan 2001 21:32:24 +0300 (MSK) |
| Cc: | gleb@xxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20010116121252.B1299@doit.wisc.edu> from "James R. Leu" at Jan 16, 1 12:12:52 pm |
| Sender: | owner-netdev@xxxxxxxxxxx |
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. Alexey |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: netlink drops messages., kuznet |
|---|---|
| Next by Date: | Re: netlink drops messages., James R. Leu |
| Previous by Thread: | Re: netlink drops messages., James R. Leu |
| Next by Thread: | Re: netlink drops messages., James R. Leu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |