lkml.org 
[lkml]   [1998]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: setsockopt(RCVBUF) Invalid argument with 2.1.103
On Wed, Jun 03, 1998 at 11:38:14AM +0100, Alan Cox wrote:
> > I do not plan to change the default {r,w}mem setting but I would like
> > to change their max settings. A) it doesn't hurt to allow 200K
> > buffers, b) a lot of software actually tries to set this (nfsd is one
> > if I remember correctly).
>

> 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?

astor

--
Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway
http://www.guardian.no/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.087 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site