[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #51908] PPPOS uses PBUF_POOL in transmit pathway
|
From: |
Joel Cunningham |
|
Subject: |
[lwip-devel] [bug #51908] PPPOS uses PBUF_POOL in transmit pathway |
|
Date: |
Thu, 14 Jun 2018 09:28:17 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 |
Follow-up Comment #6, bug #51908 (project lwip):
I think you can still use PBUF_RAM here, we just need to choose a
pre-allocated size and maybe introduce a define for it. See
pppos_output_append() where it uses PBUF_POOL_BUFSIZE to determine the maximum
size
>From what I can tell, there's nothing about PBUF_POOL_BUFSIZE that is specific
to pppos. The author must have chosen it rather than introduce a new mechanism
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?51908>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/