[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [task #12722] Improve IPv4/v6 address handling
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [task #12722] Improve IPv4/v6 address handling |
Date: |
Sat, 29 Jun 2013 20:11:43 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36 |
URL:
<http://savannah.nongnu.org/task/?12722>
Summary: Improve IPv4/v6 address handling
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: goldsimon
Submitted on: Sa 29 Jun 2013 20:11:41 GMT
Category: IPv6
Should Start On: Sa 29 Jun 2013 00:00:00 GMT
Should be Finished on: Sa 29 Jun 2013 00:00:00 GMT
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
Effort: 0.00
_______________________________________________________
Details:
One thing I'm still not happy with in integrating IPv6 is the ipX_addr_t
implementation. As a union, it covers both IPv4 and IPv6 addresses but once
you have it detached from its pcb, you can't tell wether it is v4 or v6.
When introducing ipX_addr_t, I did that to save space, but I don't think it's
worth the effort: it's currently 16 bytes and adding 1 extra byte at the end,
it would be 17 bytes, or 20 bytes where alignment follows in structs.
Summed up, this means that we need more memory, but I think systems
implementing IPv6 don't count memory in bytes but rather KBytes, anyway, or am
I wrong?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?12722>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.nongnu.org/
- [lwip-devel] [task #12722] Improve IPv4/v6 address handling,
Simon Goldschmidt <=