>On Thu, 11 Feb 1999 09:15:29 -0800
> "Justin C. Walker" wrote:
>
> > I can say that our implementation doesn't seem to =
> > suffer from this problem. Could be there's an issue in the use of =
> > PRUS_* v. the socket state we use. The code in my kernel looks like:
>
>The NetBSD code looks p
On Thu, 11 Feb 1999 09:15:29 -0800
"Justin C. Walker" wrote:
> I can say that our implementation doesn't seem to =
> suffer from this problem. Could be there's an issue in the use of =
> PRUS_* v. the socket state we use. The code in my kernel looks like:
The NetBSD code looks pretty muc
some, I'm sure, can count them :-}) hours of thrashing for web server, file server, and other-server types of uses, and haven't seen any (reports of) leakage like this.
I'll look more closely at the results we see, to verify that we don't have a problem.
Regards,
Justin
From
After a while, I have determined the cause of the leak to be the
following commit. Although, I can't seem to find any reason why
it would cause this behavior--reverting these files fixes it.
Any thoughts?
fenner 1999/01/20 09:32:01 PST
Modified files:
sys/kern uipc_socket.
