Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58494 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751331Ab0BJIXm (ORCPT ); Wed, 10 Feb 2010 03:23:42 -0500 Date: Wed, 10 Feb 2010 09:21:38 +0100 From: Stanislaw Gruszka To: reinette chatre Cc: Andrew Morton , "lkml@Think-Future.de" , Linux Kernel-Liste , "ilw@linux.intel.com" , "linux-wireless@vger.kernel.org" Subject: Re: PROBLEM: iwlagn kernel 2.6.32.3 ooops Message-ID: <20100210082137.GA2519@dhcp-lab-161.englab.brq.redhat.com> References: <20100206170348.GB9411@localhost> <20100208143118.e8e5a1ee.akpm@linux-foundation.org> <20100209165247.GB2512@dhcp-lab-161.englab.brq.redhat.com> <1265735092.2551.1835.camel@rchatre-DESK> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1265735092.2551.1835.camel@rchatre-DESK> Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi On Tue, Feb 09, 2010 at 09:04:52AM -0800, reinette chatre wrote: > I do not understand your goal here ... as seen in this trace > pci_alloc_consistent itself already calls dma_alloc_coherent right away. We can call dma_alloc_coherent with GFP_KERNEL, pci_alloc_consistent is more or less equal to dma_alloc_coherent with GFP_ATOMIC flag. Stanislaw