netdev
[Top] [All Lists]

Re: PATCH Re: udp weirdness

To: cfriesen@xxxxxxxxxxxxxxxxxx (Chris Friesen)
Subject: Re: PATCH Re: udp weirdness
From: kuznet@xxxxxxxxxxxxx
Date: Tue, 1 Oct 2002 20:41:48 +0400 (MSD)
Cc: hadi@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <3D99CA6D.5020808@xxxxxxxxxxxxxxxxxx> from "Chris Friesen" at Oct 1, 2 12:16:45 pm
Sender: netdev-bounce@xxxxxxxxxxx
Hello!

> Hmm...so even with IP_RECVERR I may not be notified if the packet is 
> dropped?

Do you not jest occasionally? :-) "Even" sounds interesting, because
this kind of errors cannot be reported _principially_ without IP_RECVERR,
providing asynchronous error reporting.

Packet can be dropped, damaged _after_ they are successfully queued
to the device. And this need not to be emphasized in documentation
on IP_RECVERR, except for a section "FUTURE DEVELOPMENT".


> either a) got out onto the wire, or b) my app got an error message back 
> explaining why the message didn't get onto the wire so that it can 
> decide how to proceed.

Then use IP_RECVERR. It reports all the errors which are detectable.

Alexey


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