Live data from Hacker News

WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

github.com

11–20 of 51 posts

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#11
post #9

It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.

It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.

my 15 year old Macbook does IPv6 and IPv4 effortlessly

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#12
post #9

It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.

It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.

Eh. IPv6 is probably cheaper to run compared to running large scale CGNAT. It's well deployed in mobile and in areas without a lot of legacy IPv4 assignments. Most of the high traffic content networks support it, so if you're an eyeball network, you can shift costs away from CGNAT to IPv6. You still have to do both though.

Is it my favorite? No. Is it well supported? Not everywhere. Is it going to win, eventually? Probably, but maybe IPv8 will happen, in which case maybe they learn and it it has a 10 years to 50% of traffic instead of 30 years to 50% of traffic.

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#14
post #9

It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.

It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.

> the only thing keeping it alive is people being overly zealous over it

Hard disagree. It turned out to be great for mobile connectivity and IoT (Matter + Thread).

> the cost to administer it is like '50'.

I'm not sure if that's true. It feels like less work to me because you don't need to worry about NAT or DHCP as much as you need with IPv4.

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#16
post #15

Are there TCP/IP stacks out there in common use that are allocating memory all the time?

Packets and sockets have to be stored in memory somehow. If you have a fixed pool that you reuse it's basically a slab allocator.

You need some memory but that doesn't mean you would constantly allocate memory. There is a big difference between a few allocations and allocating in a hot loop.

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#17
post #8

passt (the network stack that you might be using if you're running qemu, or podman containers) also has no dynamic memory allocations. I always thought it's quite an interesting achievement. https://blog.vmsplice.net/2021/10/a-new-approach-to-usermode... https://passt.top/passt/about/#security

[deleted]

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#19

Are there TCP/IP stacks out there in common use that are allocating memory all the time?

Yes, TCP is pretty hungry for buffers. The bandwidth*delay product can eat gigs of memory on a server. You have to be ready to retransmit anything that's in flight / haven't received the ack for yet.

Re: WolfIP: Lightweight TCP/IP stack with no dynamic memory allocations

#20
post #9

It only implements IPv4 which explains to a degree that why IPv6 isn't ubiquitous: it's costly to implement.

It's just not worth it. the only thing keeping it alive is people being overly zealous over it. if the cost to implement is measured as '1', the cost to administer it is like '50'.

what. have you seen ipv4 block pricing?
Post reply on HN