Re: Small size of core QUIC library to replace TCP for embedded system

[Lars Eggert <[e-mail]>]

Hi,

On 2020-7-21, at 11:17, Jupiter <[e-mail]> wrote:
> I am running Linux on iMX6ULZ using
> all sorts of open source libraries in C and C++.

if your hardware can run Linux, most of the current open source stacks (see https://github.com/quicwg/base-drafts/wiki/Implementations) should be small enough to work. But I wouldn't call it an embedded system then...

> Thanks for the links, I have to admit, my QUIC knowledge is limited, I
> thought QUIC should be a user space program, anything talking to low
> layers through Linux kernel API,

That is how most implementations work, correct.

But constrained-resource embedded devices at the low end often can't run Linux or another full-fledged OS. Many hence link together an application with only the required bits of a library OS (RIOT, Zephyr, FreeRTOS & derivatives) and run that statically on bare metal.

> seems you have to alter Ethernet RX /
> TX for QUIC, does that mean you have to alter WiFi or other media
> communications as well? My WiFi is currently supported by Linux open
> source mwifiex.

You do not need to do this for QUIC, only when you want to run on embedded boards that don't have a capable-enough Socket API interface.

>> It should be reasonably straightforward to add a packet I/O backend for
>> other IoT platforms to warpcore, (https://github.com/NTAP/warpcore) which is
>> quant's packet I/O library. I had been considering Zephyr support, but ran
>> out of time.
> 
> Looks very good, I suppose I should be able to run it on an Ubuntu 18
> laptop, right?

It will run on Linux without changes (my public test server runs Ubuntu).

Lars