lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] IP frag/reassembly


From: Jonathan Larmour
Subject: [lwip-users] IP frag/reassembly
Date: Thu, 26 Oct 2006 13:50:06 +0100
User-agent: Thunderbird 1.5.0.7 (X11/20060913)

Is there any reason why it wouldn't be possible to eliminate the MTU sized buffer used by ip_frag.c? It seems to me that it would not be hard to create a chain of pbufs of type PBUF_REF which have the payload pointing directly into the payloads of the pbuf chain being sent. If no-one sees any reason why this wouldn't work, I'll put this on my todo list, and I might be able to do it in the context of my current project.

Secondly the configurability of ip_frag.c isn't great. I think both MAX_MTU and IP_REASS_BUFSIZE are important values which should be settable options from lwipopts.h - ip_frag.c takes 7374 bytes of RAM in total, ouch. While we're there, there's also less important options such as IP_REASS_MAXAGE and IP_REASS_TMO.

It's a simple enough patch for the latter. Do I just send patches here? I should have more patches to come in due course.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
------["The best things in life aren't things."]------      Opinions==mine





reply via email to

[Prev in Thread] Current Thread [Next in Thread]