From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Tony Petz" <agoston.petz@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Running multiple concurrent TCP stacks
Date: Wed, 23 May 2007 15:22:51 -0700 [thread overview]
Message-ID: <20070523152251.0f12cbd7@localhost> (raw)
In-Reply-To: <103513710705231459l49add2a6xa9c4609d11e478a2@mail.gmail.com>
On Wed, 23 May 2007 16:59:02 -0500
"Tony Petz" <agoston.petz@gmail.com> wrote:
> I'm working on a research project that requires two simultaneously
> running but independent TCP implementations. Searching the archives I
> was only able to come up with this:
> http://www.spinics.net/lists/linux-net/msg09064.html
>
> I was wondering if anyone had any insight into the problem, or knew of
> a good place to start looking at how to load two copies of TCP stack,
> probably bound to two different interfaces for simplicity.
>
> Any advice appreciated...
> -tony
Do it in UML or other virtualization environment
prev parent reply other threads:[~2007-05-23 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 21:59 Running multiple concurrent TCP stacks Tony Petz
2007-05-23 22:22 ` Stephen Hemminger [this message]
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=20070523152251.0f12cbd7@localhost \
--to=shemminger@linux-foundation.org \
--cc=agoston.petz@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).