lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] more about SO_REUSE and UDP


From: christiaan . simons
Subject: [lwip-devel] more about SO_REUSE and UDP
Date: Tue, 23 Mar 2004 15:53:29 +0100




Hi Leon, Kieran,

Leon, there are still some #ifdef's instead of #if's for SO_REUSE in udp.c,
(and the #ifndef can be turned into a #if SO_REUSE == 0).

Or better, can Kieran or Florian indicate if they really need patch #1399?
If it isn't used, and it is not tested, err, why not remove it?
(and keep things really simple and light weight...)

It looks likes the patch changes the behaviour of the PCB API.

A radical idea: maybe the (udp) pcb list could be turned into
some sort of (c++ like) map where only unique entries are stored.

This keeps the list as short as possible, and improves search
speed for unwanted (netbios etc) traffic. Sorting the list as Leon
mentioned previously works for wanted (reference counted) traffic only.

Bye,

Christiaan

The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed. Axon Digital Design Group is neither liable for the proper nor
for the complete transmission of the information contained in this
communication nor for any delay in its receipt. Axon Digital Design Group
does not guarantee that the integrity of this communication has been
maintained nor that the communication is free of viruses, interceptions or
interference. If you are not the intended recipient of this communication,
you are hereby notified that reading, disseminating, distributing or
copying this message is strictly prohibited. In that case please return the
communication to the sender and delete and destroy all copies. In carrying
out its engagements, Axon Digital Design Group applies general terms and
conditions, which contain a clause that limits its liability. A copy of
these terms and conditions is available on request free of charge.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]