All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: E1000 - page allocation failure - saga continues :(
Date: Mon, 18 Apr 2005 14:34:57 +0200	[thread overview]
Message-ID: <20050418123457.GF26030@mail.muni.cz> (raw)
In-Reply-To: <4263A70F.5060409@univ-nantes.fr>

On Mon, Apr 18, 2005 at 02:24:47PM +0200, Yann Dupont wrote:
> >I know that kernel 2.6.6-bk4 works. So were there some memory manager changes
> >since 2.6.6? If so it looks like there are some bugs. 
> >On the other hand, ethernet driver should not allocate much memory but rather
> >drop packets.
> >
> >Btw, are you using some TCP tweaks? E.g. I have default TCP window size 1MB.
> >
> No tweaking at all. No jumbo frames.

There were assumptions that it is XFS related. Are you using XFS on that box?

I'm able to deterministically produce this error:
on XFS partition store a file from network using multiple threads. If file size
is bigger then total memory, then it fails after major part of memory is used
for a file cache.

-- 
Lukáš Hejtmánek

  reply	other threads:[~2005-04-18 12:35 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 [this message]
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
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=20050418123457.GF26030@mail.muni.cz \
    --to=xhejtman@mail.muni.cz \
    --cc=Yann.Dupont@univ-nantes.fr \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.