Re: setsockopt(RCVBUF) Invalid argument with 2.1.103
Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 3 Jun 1998 23:28:48 +0100 (BST)
> > Until Linus wakes up and allows a per user resource management
> > facility and includes committed physical memory in it (which btw
> > cleans up mlock and fixes the PTE problems) its not possible. In
> > fact for 2.1.x even the existing defaults are unsafe and broken. It
> > isnt however a networking problem really its a resource problem.
>
>
> Do you have a design and/or a patch?
Design yes, although sct is now picking holes in it on irc (he has the
advantage of having hacked on VMS which did this bit right for a long time)
anbd has also pointed out it solves the RTNONBLOCK issues with real time
signal queue sizes locked pages and the like.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu