netdev - Re: page allocation failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 14 Jun 2008 22:36:02 +0100
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Denys Fedoryshchenko <denys@...p.net.lb>
Cc:	Evgeniy Polyakov <johnpol@....mipt.ru>, netdev@...r.kernel.org
Subject: Re: page allocation failure

Denys Fedoryshchenko wrote:
> There is no jumbo frames in this particular setup.
> Probably it is getting out of memory (rtorrent using almost all for fs caching
> maybe).
[...]

The "order: 3" means an allocation of 8 pages (32 KB) at once, which
should not be needed for receiving standard Ethernet frames.  Looking
at the bnx2 code I can't see any case in which it would allocate an
skb much larger than the MTU.

Network drivers usually try to refill the hardware RX ring immediately
after handling RX completions, at which point they are running in atomic
(non-blocking) context and large contiguous memory allocations are
relatively likely to fail even if the system has plenty of memory.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html