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] [day] [month] [year] [list]
Message-ID: <BANLkTim6eXD3NQs3LNKUwz345x-D1RdBDg@mail.gmail.com>
Date:	Sun, 29 May 2011 18:28:09 +0800
From:	Eric Miao <eric.y.miao@...il.com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
	Samuel Ortiz <samuel@...tiz.org>, netdev@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] pxa: don't ask for a buffer from DMA zone

On Sun, May 29, 2011 at 6:24 PM, Russell King - ARM Linux
<linux@....linux.org.uk> wrote:
> On Sun, May 29, 2011 at 12:42:55PM +0400, Dmitry Eremin-Solenikov wrote:
>> PXA don't have special DMA zone. And since
>> 197b59ae6e8bee56fcef37ea2482dc08414e2ac (mm: fail GFP_DMA allocations
>> when ZONE_DMA is not configured) allocation with GFP_DMA set will fail
>> with a trace like this:
>
> These buffers are never used with DMA, its only used with the PIO activity
> when in SIR mode.  When in FIR mode, and DMA is being used, we copy it to
> a block of memory allocated by dma_coherent_alloc().  So the GFP_DMA
> annotation here is redundant.
>
> And that's probably more important to document in the changelog... its not
> that PXA doesn't have a special DMA zone, it's that the driver doesn't do
> DMA on these buffers so its pointless marking them with GFP_DMA.
>

Not really sure about the whole story, but further speaking, for
architectures like
PXA and most other ARM SoCs, where DMA can happen anywhere, does this
mean we don't even need to put GFP_DMA flag when doing memory allocation?


>>  static int pxa_irda_init_iobuf(iobuff_t *io, int size)
>>  {
>> -     io->head = kmalloc(size, GFP_KERNEL | GFP_DMA);
>> +     io->head = kmalloc(size, GFP_KERNEL);
>>       if (io->head != NULL) {
>>               io->truesize = size;
>>               io->in_frame = FALSE;
>> --
>> 1.7.4.4
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@...ts.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ