netdev
[Top] [All Lists]

Re: 2.6.10-rc1-mm4 -1 EAGAIN after allocation failure was: Re: Kernel 2.

To: Stefan Schmidt <zaphodb@xxxxxxxxxxx>
Subject: Re: 2.6.10-rc1-mm4 -1 EAGAIN after allocation failure was: Re: Kernel 2.6.9 Multiple Page Allocation Failures
From: Andrew Morton <akpm@xxxxxxxx>
Date: Tue, 9 Nov 2004 18:21:29 -0800
Cc: marcelo.tosatti@xxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, piggin@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20041110020327.GE20754@xxxxxxxxxxx>
References: <20041103222447.GD28163@xxxxxxxxxxx> <20041104121722.GB8537@xxxxxxxxxx> <20041104181856.GE28163@xxxxxxxxxxx> <20041109164113.GD7632@xxxxxxxxxx> <20041109223558.GR1309@xxxxxxxxxxxx> <20041109144607.2950a41a.akpm@xxxxxxxx> <20041109235201.GC20754@xxxxxxxxxxx> <20041110012733.GD20754@xxxxxxxxxxx> <20041109173920.08746dbd.akpm@xxxxxxxx> <20041110020327.GE20754@xxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Stefan Schmidt <zaphodb@xxxxxxxxxxx> wrote:
>
> > As for the application collapse: dunno.  Maybe networking broke.  It would
>  > be interesting to test Linus's current tree, at
>  > 
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.10-rc1-bk19.gz
>  Will try that tomorrow. Would you suggest printing out show_free_areas();
>  there too? I don't know what kind of an overhead that will generate on
>  subsequent stack traces.

I don't think it'd help much - we know what's happening.

It would be interesting to keep increasing min_free_kbytes, see if you can
characterise the system's response to this setting.

<Prev in Thread] Current Thread [Next in Thread>