From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
To: Dirk Hohndel <dirk@hohndel.org>
Cc: netdev@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: surprising memory request
Date: Fri, 18 Jan 2013 10:09:30 -0800 [thread overview]
Message-ID: <20130118180930.GA15466@ppwaskie-mobl2.amr.corp.intel.com> (raw)
In-Reply-To: <20130118085818.147220.FMU5901@air.gr8dns.org>
On Fri, Jan 18, 2013 at 08:58:18AM -0800, Dirk Hohndel wrote:
>
> Running openconnect on a very recent 3.8 (a few commits before Linus cut
> RC4) I get this allocation failure. I'm unclear why we would need 128
> contiguous pages here...
>
> /D
[...]
> [66015.674074] 541777 total pagecache pages
> [66015.674075] 142 pages in swap cache
> [66015.674078] Swap cache stats: add 4420, delete 4278, find 106/118
> [66015.674080] Free swap = 9197216kB
> [66015.674082] Total swap = 9213948kB
> [66015.710738] 2094576 pages RAM
> [66015.710745] 85536 pages reserved
> [66015.710746] 1755663 pages shared
> [66015.710748] 1488520 pages non-shared
> [66015.710752] netdev: Unable to allocate 1024 tx queues
What device are you using that is trying to allocate so many Tx queues?
Assuming this is coming from the VPN device coming online; is SELinux
in enforcing mode? There have been a number of changes in the tun
driver recently around the multiqueue area with SELinux, just a theory
at this point. I can keep digging.
Cheers,
-PJ
next prev parent reply other threads:[~2013-01-18 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 16:58 surprising memory request Dirk Hohndel
2013-01-18 17:46 ` Eric Dumazet
2013-01-18 17:52 ` Stephen Hemminger
2013-01-21 5:44 ` Jason Wang
2013-01-18 17:54 ` Eric Dumazet
2013-01-21 5:21 ` Jason Wang
2013-01-18 17:59 ` David Woodhouse
2013-01-20 13:06 ` Ben Hutchings
2013-01-21 5:23 ` Jason Wang
2013-01-21 5:13 ` Jason Wang
2013-01-18 18:09 ` Waskiewicz Jr, Peter P [this message]
2013-01-18 18:11 ` Waskiewicz Jr, Peter P
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=20130118180930.GA15466@ppwaskie-mobl2.amr.corp.intel.com \
--to=peter.p.waskiewicz.jr@intel.com \
--cc=dirk@hohndel.org \
--cc=dwmw2@infradead.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).