Re: [PATCH] strict VM overcommit accounting for 2.4.32/2.4.33-pre1

[Willy Tarreau <willy@w.ods.org>]

On Fri, Dec 30, 2005 at 11:37:38AM -0800, Barry K. Nathan wrote:
> On 12/30/05, Willy Tarreau <willy@w.ods.org> wrote:
> > On Fri, Dec 30, 2005 at 07:17:46PM +0100, Arjan van de Ven wrote:
> [snip discussion not directly related to the timing of my patch submission]
> > > Also I think, to be honest, that this is a feature that is getting
> > > unsuitable for the "bugfixes only" 2.4 kernel series....
> >
> > Agreed, it really is too late IMHO, because there's a non-null risk of
> > introducing new bugs with it. It would have been cool a few months
> > earlier. That won't stop me from trying it in my own tree however ;-)
> 
> Yeah, I know it's a little bit late. I wish I had been able to get
> this done a few months ago... :(

And I wish I could stay awake 24 hours a day and 365 days a year...
Seriously, this work will not be lost because 2.6 has it. However,
if it works well, I intend to link to it from my interesting patches
page (when I finally find time to put it online).

> Oh well, even if it doesn't get into the tree, at least it looks like
> I might not be the only person to benefit from this patch. :)

Every patch which can enhance long term stability will interest people
who manage remote systems and who at least start softdog to get a chance
to reach the box after an accident.

> (BTW,
> you'll probably also want the patch I just posted, which adds
> Committed_AS to /proc/meminfo.)

I've caught it, thanks.

> -Barry K. Nathan <barryn@pobox.com>

Cheers,
Willy

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