Dear colleagues,
I'am writting my master thesis in a project using the raw API of
lwip-2.0.3. Although my implementation works, I want to understand a
certain behavior between the Nagle algorithm and the way I call (or not)
tcp_output, but I am not quite sure what is happening.
In the case of a T
LS in a analysis tool they are using. It is only for debugging
and when the software is deployed I doubt they will set send_now = 0.
MfG,
Vitor
Em qui, 11 de out de 2018 às 21:11, goldsimon escreveu:
>
>
>
> vr roriz wrote:
> >[..]
> >Then, I added the send_now control o
rity and will not intercalate each other. By doing
this I believe I am in compliance with the "multi-thread issue" of the
raw API, because any invoked LWIP function will return before any
other LWIP function starts being executed.
Em qui, 11 de out de 2018 às 21:47, goldsimon escreveu
> and only one interrupt runs at a time and isn't interrupted by another
> interrupt while using
lwIP - you should be safe.
Simon, could you clarify why nesting interrupts are a problem and
non-nesting are not? Do you mean that, if an interrupt executes lwIP
code then it should not be interrupted
is priority level based, without
time-slices.
Em sex, 26 de out de 2018 às 15:39, Jan Menzel
escreveu:
>
> On 26.10.2018 10:27, vr roriz wrote:
> >> and only one interrupt runs at a time and isn't interrupted by another
> >> interrupt while using
> > lwI
x, 26 de out de 2018 às 18:29, Jan Menzel
escreveu:
> On 26.10.2018 15:57, vr roriz wrote:
> >> Vitor, make sure your processes are never cycled by the scheduler
> > otherwise you'll violate the threading requirements. I'd suggest to just
> > have a single threa
Dear colleagues,
I'm bit confused about the the TCP_WND option parameter.
First I understood that this value is the initial advertised TCP window
size. For instance, when I set it to 2*TCP_MSS, my advertised window in
the TCP header of the SYNC segment is matches 2*TCP_MSS. Also, we can se
that
it is acknowledged by the remote side
(although this buffer size can still be controlled by TCP_SND_BUF and
TCP_SND_QUEUELEN)"
What TCP_WND has to do with the amount of data to be buffered when
transmitting?
Em qui, 15 de nov de 2018 às 11:33, goldsi...@gmx.de
escreveu:
> On 15.11.2018 11:12, v
