netdev
[Top] [All Lists]

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

To: Nick Piggin <piggin@xxxxxxxxxxxxxxx>
Subject: Re: 2.6.10-rc1-mm4 -1 EAGAIN after allocation failure was: Re: Kernel 2.6.9 Multiple Page Allocation Failures
From: Stefan Schmidt <zaphodb@xxxxxxxxxxx>
Date: Wed, 10 Nov 2004 13:06:24 +0100
Cc: Andrew Morton <akpm@xxxxxxxx>, marcelo.tosatti@xxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20041110102854.GI20754@xxxxxxxxxxx>
References: <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> <419197EA.9090809@xxxxxxxxxxxxxxx> <20041110102854.GI20754@xxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
On Wed, Nov 10, 2004 at 11:28:54AM +0100, Stefan Schmidt wrote:
> > Can you try the following patch, please? It is diffed against 2.6.10-rc1,
> > but I think it should apply to -mm kernels as well.
I did. No apparent change with mm4 and vm.min_free_kbytes = 8192. I will try
latest bk next.

> I unset CONFIG_PACKET_MMAP and i suppose this could have this kind of effect
> on high connection rates.
> I set it back to CONFIG_PACKET_MMAP=y and if the application does not freeze
> for some hours at this load we can blame at least this issue (-1 EAGAIN) on
> that parameter.
Nope, that didn't change anything, still getting EAGAIN, checked two times.

        Stefan

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