Re: Linux2.6 overcommit behaviour
От | Andrew Dunstan |
---|---|
Тема | Re: Linux2.6 overcommit behaviour |
Дата | |
Msg-id | 3F4DEA80.60607@dunslane.net обсуждение исходный текст |
Ответ на | Linux2.6 overcommit behaviour (Shridhar Daithankar <shridhar_daithankar@persistent.co.in>) |
Ответы |
Re: Linux2.6 overcommit behaviour
Re: Linux2.6 overcommit behaviour |
Список | pgsql-hackers |
Yes, in 2.6, which is not yet released. Even after it is released I expect it to take some time to bed down and make its way into vendor releases, if the history of 2.4 is anything to go by. Incidentally, it looks to me like it is only in 2.6 if your kernel is built with CONFIG_SECURITY, which I expect most will be. andrew Shridhar Daithankar wrote: >Hi all, > >Following is from Documentation/vm/overcommit-accounting >------------- >2 - (NEW) strict overcommit. The total address space commit > for the system is not permitted to exceed swap + a > configurable percentage (default is 50) of physical RAM. > Depending on the percentage you use, in most situations > this means a process will not be killed while accessing > pages but will receive errors on memory allocation as > appropriate. >------------- > >Looks like it's been taken care once for all. > > Shridhar > > >---------------------------(end of broadcast)--------------------------- >TIP 4: Don't 'kill -9' the postmaster > > >
В списке pgsql-hackers по дате отправления: