* How to submit a new module to linux kernel?
@ 2006-05-22 7:18 #ZHOU BIN#
2006-05-22 13:25 ` James Morris
2006-05-22 16:06 ` Erik Mouw
0 siblings, 2 replies; 4+ messages in thread
From: #ZHOU BIN# @ 2006-05-22 7:18 UTC (permalink / raw)
To: netdev
Hi all,
I'm new in this mailing list. I implemented a new TCP congestion control module for linux kernel 2.6.16.13.
Does anybody know how to apply for the integration of it into the linux kernel? How long will this process take?
Thank you very much.
Best Regards,
Zhou Bin
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to submit a new module to linux kernel?
2006-05-22 7:18 How to submit a new module to linux kernel? #ZHOU BIN#
@ 2006-05-22 13:25 ` James Morris
2006-05-22 16:06 ` Erik Mouw
1 sibling, 0 replies; 4+ messages in thread
From: James Morris @ 2006-05-22 13:25 UTC (permalink / raw)
To: #ZHOU BIN#; +Cc: netdev
On Mon, 22 May 2006, #ZHOU BIN# wrote:
> Hi all,
>
> I'm new in this mailing list. I implemented a new TCP congestion control module for linux kernel 2.6.16.13.
> Does anybody know how to apply for the integration of it into the linux kernel? How long will this process take?
Read Documentation/SubmittingPatches, then send the patch here.
If it's a good patch, it could be integrated quickly.
--
James Morris
<jmorris@namei.org>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to submit a new module to linux kernel?
2006-05-22 7:18 How to submit a new module to linux kernel? #ZHOU BIN#
2006-05-22 13:25 ` James Morris
@ 2006-05-22 16:06 ` Erik Mouw
2006-05-22 21:41 ` Ian McDonald
1 sibling, 1 reply; 4+ messages in thread
From: Erik Mouw @ 2006-05-22 16:06 UTC (permalink / raw)
To: #ZHOU BIN#; +Cc: netdev
On Mon, May 22, 2006 at 03:18:12PM +0800, #ZHOU BIN# wrote:
> I'm new in this mailing list. I implemented a new TCP congestion
> control module for linux kernel 2.6.16.13.
> Does anybody know how to apply for the integration of it into the
> linux kernel? How long will this process take?
See Documentation/SubmittingPatches in your kernel tree.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to submit a new module to linux kernel?
2006-05-22 16:06 ` Erik Mouw
@ 2006-05-22 21:41 ` Ian McDonald
0 siblings, 0 replies; 4+ messages in thread
From: Ian McDonald @ 2006-05-22 21:41 UTC (permalink / raw)
To: Erik Mouw; +Cc: #ZHOU BIN#, netdev
On 5/23/06, Erik Mouw <erik@harddisk-recovery.com> wrote:
> On Mon, May 22, 2006 at 03:18:12PM +0800, #ZHOU BIN# wrote:
> > I'm new in this mailing list. I implemented a new TCP congestion
> > control module for linux kernel 2.6.16.13.
> > Does anybody know how to apply for the integration of it into the
> > linux kernel? How long will this process take?
>
> See Documentation/SubmittingPatches in your kernel tree.
>
>
I would also add that for this type of patch a peer reviewed paper
outlining the congestion control work would be useful/needed.
Every person wants to improve TCP and has written a congestion control
mechanism (myself included!) but that doesn't mean it is worth
including in the kernel (mine certainly isn't....).
In particular for TCP congestion control you need to show in what
cases it is better than others, what cases it is worse and how fair is
it compared to other TCP flows.
Ian
--
Ian McDonald
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group
Department of Computer Science
University of Waikato
New Zealand
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-05-22 21:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-22 7:18 How to submit a new module to linux kernel? #ZHOU BIN#
2006-05-22 13:25 ` James Morris
2006-05-22 16:06 ` Erik Mouw
2006-05-22 21:41 ` Ian McDonald
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).