Darren Reed wrote:

> What I read out of all this is that there's not likely to be
> one answer for how all ULP properties are to be handled.


I think we should put this in perspective.  Those
tunables should not need to be changed in the first
place.  So extending the method of changing them to
a per interface basis seems to be finding a problem
for a solution.  Instead we should try to eliminate
most of the reasons those tunables need to be changed.


> For example, if I were to take the above comment from
> Kacheong and reference TCP timeouts, then it may be
> that picking the "right set" at connect() time when the
> local address is assigned is the right thing to do and not
> when the socket is created or just bound.


By "right set," do you mean "right set of TCP timeouts?"
Usually, it is not recommended to change those TCP timeout
values.  And they can be changed on a per connection
basis already.  Or do you refer to the previous example
about picking an anonymous port?  In that case, we must
pick the port at bind() time.  Otherwise, those apps which
do a getsockname() after the bind() will no longer work.


> Or maybe that's just all too dangerous and should be
> left to instances to solve?





-- 

                                                K. Poon.
                                                kacheong.poon at sun.com


Reply via email to