Re: /proc/<n>/maps getting _VERY_ long

Linus Torvalds (torvalds@transmeta.com)
Mon, 6 Aug 2001 01:01:40 +0000 (UTC)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: H. Peter Anvin: "Re: /proc/<n>/maps getting _VERY_ long"
Previous message: Michael H. Warfield: "Re: /proc/<n>/maps getting _VERY_ long"
Maybe in reply to: Chris Wedgwood: "/proc/<n>/maps getting _VERY_ long"
Next in thread: H. Peter Anvin: "Re: /proc/<n>/maps getting _VERY_ long"

In article <20010805204143.A18899@alcove.wittsend.com>,
Michael H. Warfield <mhw@wittsend.com> wrote:
>On Sun, Aug 05, 2001 at 04:41:43PM -0700, Linus Torvalds wrote:
>
>> We could merge more, but I'm not interested in working around broken
>
> If it only causes problems for the broken app, that's fine. If it
>causes problems for the rest of the system, that could be bad.

It only causes problem for the broken app. Even then, the problem is a
(likely undetectable) slowdown, or in the extreme case the kernel will
just tell it that "Ok, you've allocated enough, no more soup for you".

Linus
-
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/

Next message: H. Peter Anvin: "Re: /proc/<n>/maps getting _VERY_ long"
Previous message: Michael H. Warfield: "Re: /proc/<n>/maps getting _VERY_ long"
Maybe in reply to: Chris Wedgwood: "/proc/<n>/maps getting _VERY_ long"
Next in thread: H. Peter Anvin: "Re: /proc/<n>/maps getting _VERY_ long"