Re: Coordinating TCP projects

2008-01-21 Thread Andre Oppermann
James Healy wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre Oppermann wrote: The first cut is now at //depot/projects/tcp_reass/ however I made a mistake when creating the branch and now the code is in the same changeset as the branching itself. Doesn't make it easy to do a diff. H

Re: Coordinating TCP projects

2008-01-20 Thread James Healy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre Oppermann wrote: > The first cut is now at //depot/projects/tcp_reass/ however I made > a mistake when creating the branch and now the code is in the same > changeset as the branching itself. Doesn't make it easy to do a > diff. Have to see how

Re: Coordinating TCP projects

2008-01-16 Thread Giorgos Keramidas
On 2008-01-11 03:19, Andre Oppermann <[EMAIL PROTECTED]> wrote: >Lawrence Stewart wrote: >>> I've got a rewritten and much more efficient tcp_reass() function in >>> my local tree. I'll import it into Perforce next week with all the >>> other stuff. You may want to base your auto-sizing work on i

Re: Coordinating TCP projects

2008-01-10 Thread Andre Oppermann
Lawrence Stewart wrote: I've got a rewritten and much more efficient tcp_reass() function in my local tree. I'll import it into Perforce next week with all the other stuff. You may want to base your auto-sizing work on it. The only missing parts are some statistics gathering. Where abouts is

Transport layer congestion control ideas (was Re: Coordinating TCP projects)

2008-01-10 Thread Lawrence Stewart
Hi Randall, Comments inline... Randall Stewart wrote: Robert: One thing I would like to point out for one of Lawrence's project is that SCTP is also hanging around in the kernel and as part of one of our URP's (which is also where Lawrence's project came from.. if I remember right)... we added

Re: Coordinating TCP projects

2008-01-10 Thread Randall Stewart
Robert: One thing I would like to point out for one of Lawrence's project is that SCTP is also hanging around in the kernel and as part of one of our URP's (which is also where Lawrence's project came from.. if I remember right)... we added "selectable" congestion control to SCTP.. well it was no

Re: Coordinating TCP projects

2008-01-10 Thread Andre Oppermann
Lawrence Stewart wrote: Hi Andre, Andre Oppermann wrote: Lawrence Stewart wrote: [snip] Jim and I recently discussed the idea of implementing autotuning of the TCP reassembly queue size based on analysis of some experimental work we've been doing. It's a small project, but we feel it would

Re: Coordinating TCP projects

2008-01-09 Thread Lawrence Stewart
Hi Andre, Andre Oppermann wrote: Lawrence Stewart wrote: [snip] Jim and I recently discussed the idea of implementing autotuning of the TCP reassembly queue size based on analysis of some experimental work we've been doing. It's a small project, but we feel it would be worth implementing.

Re: Coordinating TCP projects

2007-12-20 Thread Brooks Davis
On Wed, Dec 19, 2007 at 01:09:13PM +, Robert Watson wrote: > > I'd like for us to create a wiki page tracking these various projects, and > pointing at per-project resources. Once the discussion has settled a bit, > I can take responsibility for creating such a page, but will need everyone

Re: Coordinating TCP projects

2007-12-20 Thread Andre Oppermann
Lawrence Stewart wrote: Hi Robert, Comments inline. Robert Watson wrote: Dear all, It is rapidly becoming clear that quite a few of us have Big Plans for the TCP implementation over the next 12-18 months. It's important that we get the plans out on the table now so that everyone working o

Re: Coordinating TCP projects

2007-12-19 Thread Lawrence Stewart
Hi Robert, Comments inline. Robert Watson wrote: Dear all, It is rapidly becoming clear that quite a few of us have Big Plans for the TCP implementation over the next 12-18 months. It's important that we get the plans out on the table now so that everyone working on these projects is awar

Coordinating TCP projects

2007-12-19 Thread Robert Watson
Dear all, It is rapidly becoming clear that quite a few of us have Big Plans for the TCP implementation over the next 12-18 months. It's important that we get the plans out on the table now so that everyone working on these projects is aware of the larger context. This will encourage collab