lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] Re: [task #7040] Work on tcp_enqueue


From: address@hidden
Subject: [lwip-devel] Re: [task #7040] Work on tcp_enqueue
Date: Sun, 01 Feb 2009 15:50:40 +0100
User-agent: Thunderbird 2.0.0.19 (Macintosh/20081209)

Jakob Stoklund Olesen wrote:
Not a problem, it is not allowed. From tcp_enqueue prolog:

  LWIP_ERROR("tcp_enqueue: len == 0 || optlen == 0 (programmer violates API)",
      ((len == 0) || (optlen == 0)), return ERR_ARG;);
  LWIP_ERROR("tcp_enqueue: arg == NULL || optdata == NULL (programmer violates 
API)",
      ((arg == NULL) || (optdata == NULL)), return ERR_ARG;);



That's fine, then.

Sure, but UDP performance is rarely critical, and it seems wasteful to
extend struct pbuf just for that.

I wouldn't think so. If you want high throughput and can cope with lost segments, UDP is the better alternative to TCP and would still require high throughput! However, the goal of that patch (and its discussion) was to NOT include another member in struct pbuf but to solve it in a different way (which is why it is still open and not finished).


Simon




reply via email to

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