public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: E1000 - page allocation failure - saga continues :(
Date: Tue, 19 Apr 2005 10:15:27 +0200	[thread overview]
Message-ID: <4264BE1F.50508@univ-nantes.fr> (raw)
In-Reply-To: <1113897810.5074.66.camel@npiggin-nld.site>

Nick Piggin a écrit :

>
>>Do you have turned NAPI on ??? I tried without it off on e1000 and ...
>>surprise !
>>Don't have any messages since 12H now (usually I got those in less than 1H)
>>
>>    
>>
>
>Possibly kswapd might be unable to get enough CPU to free memory.
>
>  
>
Ok, so what you're saying is that turning NAPI off is just slowing down
things enough to not be hit by
this problem , right ?


-- 
Yann Dupont, Cri de l'université de Nantes
Tel: 02.51.12.53.91 - Fax: 02.51.12.58.60 - Yann.Dupont@univ-nantes.fr


  reply	other threads:[~2005-04-19  8:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 21:48 E1000 - page allocation failure - saga continues :( Lukas Hejtmanek
2005-04-18 12:10 ` Yann Dupont
2005-04-18 12:22   ` Lukas Hejtmanek
2005-04-18 12:24     ` Yann Dupont
2005-04-18 12:34       ` Lukas Hejtmanek
2005-04-18 12:39         ` Yann Dupont
2005-04-19  7:23     ` Yann Dupont
2005-04-19  8:03       ` Nick Piggin
2005-04-19  8:15         ` Yann Dupont [this message]
2005-04-19  8:24           ` Nick Piggin
2005-04-19  9:34           ` Lukas Hejtmanek
2005-04-19  8:04       ` Lukas Hejtmanek
2005-04-20  3:42         ` Nuno Silva
2005-04-20  7:12         ` Yann Dupont
  -- strict thread matches above, loose matches on Subject: below --
2005-05-10  8:06 linuxkernel2.20.sandos
2005-05-10  8:19 ` Nick Piggin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4264BE1F.50508@univ-nantes.fr \
    --to=yann.dupont@univ-nantes.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=xhejtman@mail.muni.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox