All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric <eric@cisu.net>
To: sks@alum.mit.edu, linux-newbie@vger.kernel.org
Subject: Re: TCP as a module
Date: Sun, 27 Jul 2003 10:19:19 -0500	[thread overview]
Message-ID: <200307271019.19111.eric@cisu.net> (raw)
In-Reply-To: <000501c3538a$2cd22e30$6400a8c0@bombay>

Have you tried CC'ing linux-kernel mailing list?
I could be wrong but linux-newbie seems a bit out of place for a post dealing 
with kernel code development.

the address is 
linux-kernel@vger.kernel.org
and you can subscribe at www.kernel.org

Just a suggestion, I hope you find the answers you're looking for there.

On Saturday 26 July 2003 10:25 am, Shan Sinha wrote:
> Hi everyone-
>
> My web searches on this seem to turn up very little.
>
> Many people have suggested that TCP as a loadable module would be nice.
> I am actually in a position where I think it might be necessary.
>
> I am working on a research project on an ad-hoc 802.11 network spanning
> through a local neighborhood.  There are multiple people developing on
> the network with dozens of nodes all running 2.4.  Various kernels
> across the network are updated at various times, but upgrades do happen
> frequently.  Occassionally, kernels are uniformally updated across the
> entire network.
>
> My work specifically requires some TCP hacking.  As a result, I would
> like to insulate my work from other kernel upgrades, so as not to have
> to redo work.  Creating an isolated sandbox, while possible, is not
> optimal, b/c the kernel upgrades are usually necessary and worth
> incorporating.
>
> As a result, I would like to implement a new transport layer module
> based on the TCP code, but with its own address family.  I realize I
> might have to re-compile a few tools, but I use few enough of those,
> that it should be no problem.
>
> Looking at the code, I assume that a starting step would be to figure
> out how to implement TCP as a module.
>
> + Has anyone actually done this or know of someone who has?  Any
> advice/links would be useful.
> + Or does anyone know for certain that doing this is just not possible?
> If so, why not?
>
> I'm willing to live with idiosyncracies in how such a TCP module would
> behave for making my development life easier, I think this is necessary!
> The idea would be that once some of my work actually demonstrates
> positive results, to re-implement back into the core kernel code.
>
> If you have a better solution, I would love to hear it!
>
> Cheers-
> Shan
>
> Shan Sinha
> Networks and Mobile Systems
> Laboratory for Computer Science and AI
> MIT
>
> For information on the research project, visit
> http://pdos.lcs.mit.edu/roofnet
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

-- 

----------------------
Eric Bambach   
Eric (at) CISU (dot) net 
----------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2003-07-27 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 15:25 TCP as a module Shan Sinha
2003-07-27 15:19 ` Eric [this message]
2003-07-27 15:29   ` Mr. James W. Laferriere
  -- strict thread matches above, loose matches on Subject: below --
2016-11-06  1:10 Md. Islam
2016-11-13  5:55 ` Valdis.Kletnieks at vt.edu
2016-11-14 12:17 ` Aruna Hewapathirane
2016-11-15  5:14   ` Md. Islam
2016-11-15  6:05     ` Valdis.Kletnieks at vt.edu

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=200307271019.19111.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=sks@alum.mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.