Messages in this thread | | | Date | Thu, 15 Mar 2007 11:06:21 -0800 | From | Andrew Morton <> | Subject | Re: thread stacks and strict vm overcommit accounting |
| |
> On Tue, 13 Mar 2007 18:33:20 +0200 Dan Aloni <da-x@monatomic.org> wrote: > Hello, > > This question is relevent to 2.6.20. > > I noticed that if the RSS for the stack size is say, 8MB, running > a single-threaded process doesn't incur an increase of 8MB to > Committed_AS (/proc/meminfo). > > However, on multi-threaded apps linked with pthread (on Debian > Etch with 2.6.20 vanilla x86_64), every thread will incur the > the specified maximum stack size RSS (assuming that you use > the default attr). In other words, it appears that vm accounting > works differently in that case. > > Is this the intended behaviour?
That sounds like a bug to me. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |