Re: [PATCH 08/24] net, diet: Make TCP metrics optional
[Posted May 6, 2014 by corbet]
| From: |
| Eric Dumazet <eric.dumazet-AT-gmail.com> |
| To: |
| josh-AT-joshtriplett.org |
| Subject: |
| Re: [PATCH 08/24] net, diet: Make TCP metrics optional |
| Date: |
| Tue, 06 May 2014 09:39:19 -0700 |
| Message-ID: |
| <1399394359.15399.20.camel@edumazet-glaptop2.roam.corp.google.com> |
| Cc: |
| David Miller <davem-AT-davemloft.net>, andi-AT-firstfloor.org, netdev-AT-vger.kernel.org, linux-kernel-AT-vger.kernel.org, tom.zanussi-AT-linux.intel.com, ak-AT-linux.intel.com |
| Archive‑link: | |
Article |
On Tue, 2014-05-06 at 08:57 -0700, josh@joshtriplett.org wrote:
> A NAK isn't going to cut it, here; tiny Linux systems are going to
> exist, and they shouldn't have to maintain a long-term out-of-tree fork
> or use crazy things like LWIP.
What's wrong with user space implementations of networking stacks ?
For many usages, it can bring 10 times the performance of having user
application and kernel sockets.
In any cases, we do not model kernel implementations to 'compete' with
user space.
We simply can not compete with user space, as a programmer is free to
keep what he really wants/needs.
I have started using linux on 386/486 pcs which had more than 2MB of
memory, it makes me sad we want linux-3.16 to run on this kind of
hardware, and consuming time to save few KB here and here.
