From: Kallol Biswas <kallol@nucleodyne.com>
To: linux-kernel@vger.kernel.org
Subject: running linux TCP/IP stack on a real slow machine
Date: 20 Oct 2005 14:08:32 -0700 [thread overview]
Message-ID: <1129842512.24889.21.camel@driver> (raw)
In-Reply-To: <20051020135014.2289fa01.akpm@osdl.org>
I have been designing and developing IP cores for a system on chip
project. A system emulator (RTL) has been used to validate the cores.
The emulated system runs at several Khz (700KHz) and is real slow.
Booting linux takes more that 40 minutes. We have a bridge for the
ethernet interface to talk to outside network, and it does not terminate
TCP connections.
If a process running on such a system tries to talk a process that is
running on a normal system (like a PC) over TCP/IP protocols what will
be the issues we will find in the stack?
I have a good idea on what is going to happen. Just looking for
comments/input.
Kallol Biswas
next prev parent reply other threads:[~2005-10-20 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 16:41 [EXPERIMENT,RFC] FAT: Add "flush" option for hotplug devices OGAWA Hirofumi
2005-10-20 20:50 ` Andrew Morton
2005-10-20 21:08 ` Kallol Biswas [this message]
2005-10-22 7:45 ` OGAWA Hirofumi
2005-10-22 10:15 ` Christoph Hellwig
2005-10-22 10:45 ` OGAWA Hirofumi
2005-10-22 10:56 ` Christoph Hellwig
2005-10-22 11:24 ` OGAWA Hirofumi
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=1129842512.24889.21.camel@driver \
--to=kallol@nucleodyne.com \
--cc=linux-kernel@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