Ok, that's what I thought. I will have to re-implement sio_write().
What I'm concerned also is, sio_write() is meant to block until all
data is pushed out. This can be more than a second in a slow 9600bps
connection (still used sometimes!!!). Will PPP try to do something
during this time like try to re-send the packet or think it was lost?
I'm not familiar with the internal ppp timer processes.
It also means more dynamic memory allocation since a reference to pbuf
is not passed to sio_write().
Just thinking out loud I guess :-)
Cheers
Ivan
Date: Fri, 29 Aug 2014 22:29:17 +0200
From: Sylvain Rochet <grada...@gradator.net>
To: Mailing list for lwIP users <lwip-users@nongnu.org>
Subject: Re: [lwip-users] ppp-new threading question
Message-ID: <20140829202917.ga29...@gradator.net>
Content-Type: text/plain; charset="utf-8"
Hi Ivan,
On Fri, Aug 29, 2014 at 10:16:04AM -0600, Ivan Delamer wrote:
I feel almost embarrassed asking this but I haven't completely
figured it out yet.
In ppp-new, are packets sent to sio_write() from tcpip thread, or
from the RX process thread? Or both?
tcpip thread only.
(The stack owned RX process thread does not exist anymore, this was
broken by design).
I just ask because sio_write() may block for some time (at least in
my basic implementation) and I'm wondering if this is blocking the
rest of the stack.
Yes, it will, sio_write() should not block.
Sylvain
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
