From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
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 18:24:19 +1000 [thread overview]
Message-ID: <1113899059.5074.71.camel@npiggin-nld.site> (raw)
In-Reply-To: <4264BE1F.50508@univ-nantes.fr>
On Tue, 2005-04-19 at 10:15 +0200, Yann Dupont wrote:
> 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 ?
>
Perhaps, yes. Or that NAPI is using more CPU than non-NAPI
(which I understand can happen in some corner cases).
If you have a multiprocessor (or even hyperthreading), I
think you could test this by binding kswapd on cpu CPU, and
put nic interrupts on the other - then test with and without
NAPI.
That is, presuming you can reproduce the problem on your
multiprocessor system in the first place.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2005-04-19 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 21:48 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
2005-04-19 8:24 ` Nick Piggin [this message]
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
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=1113899059.5074.71.camel@npiggin-nld.site \
--to=nickpiggin@yahoo.com.au \
--cc=Yann.Dupont@univ-nantes.fr \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®