This is the system limit info: http://linux.about.com/library/cmd/blcmdl2_setrlimit.htm
It has nothing to do with PHP. The PHP limit is in the INI file and you can grep for that INI parameter in PHP. But again, it is something which is managed inside the Zend memory manager (zend_alloc.*) Andi > -----Original Message----- > From: bertrand Gugger [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 29, 2006 3:30 PM > To: internals@lists.php.net > Subject: Re: [PHP-DEV] does 16M give a counting overhead ? > > Andi Gutmans wrote: > > There is no hardcoded counting. We either cound > > (--enable-memory-limit) or we don't (i.e. we rely on the system > > limits) > OK , I guess I have to find out where this php , constant , > system wide limit is. > I thought the 8M limit was due to PHP , is it C doing it ? > > Thanks for the kind answers. > -- > toggg > > > > Andi > > > > > >>-----Original Message----- > >>From: bertrand Gugger [mailto:[EMAIL PROTECTED] > >>Sent: Saturday, July 29, 2006 1:10 PM > >>To: internals@lists.php.net > >>Subject: Re: [PHP-DEV] does 16M give a counting overhead ? > >> > >>Andi Gutmans wrote: > >> > >>>Hi Bertrand, > >>> > >>>The discussion is on how and what we count, not on whether > >> > >>to count or not. > >>The quoted discussion is/was , this one is about the possibility to > >>get 16M without counting. > >> > >>>If you count in 256KB increments instead of in byte > increments then > >>>there's less counting to do in order to get to 16MB :) > >> > >>Is the hardcoded 8M counting that way ? > >>( I mean , without --enable-memory-limit ) > >>-- > >>toggg > >> > >>-- > >>PHP Internals - PHP Runtime Development Mailing List To > unsubscribe, > >>visit: http://www.php.net/unsub.php > >> > > -- > PHP Internals - PHP Runtime Development Mailing List To > unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
