From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Given Subject: Re: full5 with elksnet Date: Fri, 04 Jun 2004 01:33:49 +0100 Sender: linux-8086-owner@vger.kernel.org Message-ID: <40BFC36D.7080902@cowlark.com> References: <20040603190129.32087.qmail@web51306.mail.yahoo.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040603190129.32087.qmail@web51306.mail.yahoo.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-8086@vger.kernel.org Tommy McCabe wrote: [...] > 1. Includes ktcp in full5. Hmm. What *is* ktcp? Is it a user space TCP/IP stack? If so, how does it work? One of the things I've always thought would be a good idea was to move the TCP/IP stack out of the limited kernel space into user space... has someone already done this? If so, very nice --- how big is the kernel binary without the TCP/IP code? How does it talk to the frame driver? -- [insert interesting .sig here]