On (01/19/10 16:48), Artem Kachitchkine wrote:
> On 01/14/10 11:04 AM, Kacheong Poon wrote:
> >
> > Is there a need to have a set-cong-prop command to change
> > some cc algorithm's behavior? For example, we may want to
> > be able to change max increment of cwnd for CUBIC. If we
> > have set-cong-prop, we should have show-cong-prop and reset-..
>
> I thought about that. Given our past experiences with private driver
> properties (which this is quite similar to), I came to the conclusion that
> it might not be worth the effort. That is, the usefulness of having stable
> administrative interfaces for private cong module properties is overweighted
> by the cost of implementation and ongoing maintenance. I figure that folks
> wanting such low level of control wouldn't mind setting tunables directly
> (via mdb or /etc/system).
one drawback with this approach, though, is that you can not set these
tunables on a per-stack-instance basis. I'm not sure how significant
that would be for your case.
:
> > network". So would the algorithm choice then depend on the outgoing
> > interface? the outgoing gateway? the connection destination? (since the
> > actual path taken to the destination is non-deterministic,
> > I can see all of the above as impacting factors that an admin might
> > want to use as constraints)
:
> Note however, that this is only a limitation for congestion-unaware
> applications - each process is free to switch between algorithms arbitrarily
> using the {TCP,SCTP}_CONGESTION socket option.
Ok.
--Sowmini
_______________________________________________
networking-discuss mailing list
[email protected]
