From: Bernd Petrovitsch <bernd@firmix.at>
To: nramirez@site.uottawa.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question
Date: Thu, 15 Dec 2005 10:13:49 +0100 [thread overview]
Message-ID: <1134638030.26870.24.camel@tara.firmix.at> (raw)
In-Reply-To: <3374.127.0.0.1.1134603734.squirrel@127.0.0.1>
On Wed, 2005-12-14 at 18:42 -0500, nramirez@site.uottawa.ca wrote:
[...]
> I want to implement a congestion control algorithm for an Ad-hoc wireless
> network. It means i will make some modifications to TCP and therefore in
> the transport layer.
> Do i need to modify the Kernel to do my implementation? or there are some
Yes.
> kernel modules i can modify as for the case of implementing a routing
> protocol in the network layer? If both are possible what could be the
No. You can compile the TCP/IP stack as module for easier
loading/unloading but that's all.
> advantage or disadvantage of each? Where can i get more information?
BTW almost rotuing protocols don't need changes in TCP/IP - they simple
use it as is and configure routes from the outside (of the kernel).
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2005-12-15 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 23:42 Question nramirez
2005-12-15 9:13 ` Bernd Petrovitsch [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-09 11:16 question lilofile
2014-06-07 10:02 question lilofile
2008-08-10 16:45 Question mengualjeanphi
2002-12-11 6:35 question Sipos Ferenc
2002-12-11 6:46 ` question Robert Love
2002-07-14 10:51 question Sipos Ferenc
2002-07-14 11:36 ` question jbradford
2001-05-18 3:47 Question C.Praveen
2001-05-09 20:29 Question Krishnan Ananthanarayanan
2001-03-07 23:22 Question Alberio Bathory-Frota
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=1134638030.26870.24.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=linux-kernel@vger.kernel.org \
--cc=nramirez@site.uottawa.ca \
/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).