From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: full5 with elksnet
Date: Fri, 04 Jun 2004 01:33:49 +0100 [thread overview]
Message-ID: <40BFC36D.7080902@cowlark.com> (raw)
In-Reply-To: <20040603190129.32087.qmail@web51306.mail.yahoo.com>
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]
next prev parent reply other threads:[~2004-06-04 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 19:01 full5 with elksnet Tommy McCabe
2004-06-03 21:26 ` claudio
2004-06-03 21:32 ` Tommy McCabe
2004-06-04 3:34 ` Miguel Bolanos
2004-06-04 11:35 ` claudio
2004-06-04 20:28 ` Tommy McCabe
2004-06-04 0:33 ` David Given [this message]
2004-06-05 13:11 ` claudio
2004-06-04 3:18 ` Miguel Bolanos
2004-06-09 13:42 ` ** Applied ** " Miguel Bolanos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40BFC36D.7080902@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox