[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] mem(p) allocator change request
From: |
christiaan . simons |
Subject: |
Re: [lwip-devel] mem(p) allocator change request |
Date: |
Tue, 30 Mar 2004 11:56:23 +0200 |
address@hidden wrote on 30-03-2004
10:10:23:
> >>but my question is what you mean with "externally
> >>allocated pools"?
> >
> >
> > To be more precise, pools defined outside the memp module.
> Dynamically or statically?
Statically to start with. The dynamic case implies a
system which has an allocator, and lwip assumes nothing.
> Statically wouldn't change the current situation much.
It's really a not-so-big change, but it helps implementing
new protocols in a clean way. And it might facilitate
the dynamic adding, removal or restarting of (app layer)
protocols, which isn't possible now.
That's the reason why I started the discussion.
> dynamically on the other hand would let the application use the space
when not
> needed by lwIP, but then the mem allocator would have to be able to
> tell the system when it needs a new pool.
This makes sense if lwip or parts of it are used
for a limited timespan.
I'll try to make it flexible enough to accomodate
future extensions and keep it simple at the same time.
And I'll just create a patch, to avoid a discussion
on tiny details. We'll address them later...
Christiaan
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed. Axon Digital Design Group is neither liable for the proper nor
for the complete transmission of the information contained in this
communication nor for any delay in its receipt. Axon Digital Design Group
does not guarantee that the integrity of this communication has been
maintained nor that the communication is free of viruses, interceptions or
interference. If you are not the intended recipient of this communication,
you are hereby notified that reading, disseminating, distributing or
copying this message is strictly prohibited. In that case please return the
communication to the sender and delete and destroy all copies. In carrying
out its engagements, Axon Digital Design Group applies general terms and
conditions, which contain a clause that limits its liability. A copy of
these terms and conditions is available on request free of charge.
Re: [lwip-devel] mem(p) allocator change request, lukem . lwip, 2004/03/29