linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Marc MERLIN <marc@merlins.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pavel Machek <pavel@ucw.cz>, David Rientjes <rientjes@google.com>,
	sgruszka@redhat.com, linux-wireless@vger.kernel.org,
	wey-yi.w.guy@intel.com, ilw@linux.intel.com,
	Andrew Morton <akpm@osdl.org>, Mel Gorman <mgorman@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: iwl3945: order 5 allocation during ifconfig up; vm problem?
Date: Wed, 12 Sep 2012 08:54:06 +0200	[thread overview]
Message-ID: <1347432846.4293.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20120912055712.GE11613@merlins.org> (sfid-20120912_075811_640589_74AB6505)

On Tue, 2012-09-11 at 22:57 -0700, Marc MERLIN wrote:
> On Wed, Sep 12, 2012 at 07:16:28AM +0200, Eric Dumazet wrote:
> > On Tue, 2012-09-11 at 16:25 -0700, Andrew Morton wrote:
> > 
> > > Asking for a 256k allocation is pretty crazy - this is an operating
> > > system kernel, not a userspace application.
> > > 
> > > I'm wondering if this is due to a recent change, but I'm having trouble
> > > working out where the allocation call site is.
> > > --
> > 
> > (Adding Marc Merlin to CC, since he reported same problem)
> > 
> > Thats the firmware loading in iwlwifi driver. Not sure if it can use SG.
> > 
> > drivers/net/wireless/iwlwifi/iwl-drv.c
> > 
> > iwl_alloc_ucode() -> iwl_alloc_fw_desc() -> dma_alloc_coherent()
> > 
> > It seems some sections of /lib/firmware/iwlwifi*.ucode files are above
> > 128 Kbytes, so dma_alloc_coherent() try order-5 allocations
> 
> Thanks for looping me in, yes, this looks very familiar to me :)
> 
> In the other thread, Johannes Berg gave me this patch which is supposed to
> help: http://p.sipsolutions.net/11ea33b376a5bac5.txt

Yes, but that patch won't apply to iwlegacy as is. However, I'm pretty
sure that it should be possible to solve the issue in the same way in
iwlegacy.

johannes


  reply	other threads:[~2012-09-12  6:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 21:32 iwl3945: order 5 allocation during ifconfig up; vm problem? Pavel Machek
2012-09-09 22:40 ` David Rientjes
2012-09-10 11:11   ` Pavel Machek
2012-09-11 23:25     ` Andrew Morton
2012-09-12  5:16       ` Eric Dumazet
2012-09-12  5:57         ` Marc MERLIN
2012-09-12  6:54           ` Johannes Berg [this message]
2012-09-24  9:03             ` Dan Carpenter
2012-09-24  9:14               ` Johannes Berg
2012-09-12  9:22       ` Stanislaw Gruszka
2012-09-12 10:18       ` Mel Gorman
2012-10-03 11:37         ` Stanislaw Gruszka
2012-10-03 18:07           ` David Rientjes
2012-10-05  8:37             ` Stanislaw Gruszka
2012-10-06 12:08               ` Pavel Machek
2012-10-08 15:38                 ` Stanislaw Gruszka

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=1347432846.4293.0.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=akpm@linux-foundation.org \
    --cc=akpm@osdl.org \
    --cc=eric.dumazet@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marc@merlins.org \
    --cc=mgorman@suse.de \
    --cc=pavel@ucw.cz \
    --cc=rientjes@google.com \
    --cc=sgruszka@redhat.com \
    --cc=wey-yi.w.guy@intel.com \
    /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).