lwip-users
[Top][All Lists]
Advanced

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

Re: [lwip-users] TCP_WRITE_FLAG_MORE, tcp_write(), tcp_output() and real


From: address@hidden
Subject: Re: [lwip-users] TCP_WRITE_FLAG_MORE, tcp_write(), tcp_output() and real output TCP segment
Date: Thu, 23 Nov 2017 21:59:31 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

Giuseppe Modugno wrote:
For example, httpd usually calls tcp_output() after http_send(), except when http_send() is called from http_recv(). From what you write, it's better to call tcp_output() even in http_recv().

You got that wrong. It's not better. What I meant is it doesn't harm (other than the few processor cycles until the check is executed).

What I meant is it's not worth to propagate the information about the call stack (recv or poll/sent) to a common function. As it turns out, httpd is not a good example in this respect ;-)

Simon



reply via email to

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