[lwip-devel] [bug #26133] Processor specific porting needs flexibility in terms of placement of various memory pools and heap

[Simon Goldschmidt]

Update of bug #26133 (project lwip):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #7:

As I already said in patch #6822: I think Bill's idea to include prototype of
the heap- or pool-variable definition in cc.h (including the appropriate
__attribute__ or pragme to relocate them) is good enough _plus_ it keeps us
from having _PRE and _POST defines everywhere.

Are there any architectures where this doesn't work?

Of course, there is still a limitation when pool elements shall come from
totally different areas (e.g. pbuf pool in internal, non-contiguous buffers) -
we would need a different mechanism for that. But then again, this is rather a
thing to discuss in task #7896 (Support zero-copy drivers).

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26133>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/