linux-kernel - Re: [PATCH 1/2] dw_dmac: set CAP_PRIVATE capability for DW DMA controller

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:	Tue, 31 Mar 2009 22:30:23 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Hans-Christian Egtvedt <hans-christian.egtvedt@...el.com>
CC:	"Sosnowski, Maciej" <maciej.sosnowski@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] dw_dmac: set CAP_PRIVATE capability for DW DMA controller

Hans-Christian Egtvedt wrote:
> The weird part was that when testing this, the dma_request_channel()
> would not return any channel before DMA_PRIVATE flag was set. I think I
> did this some time ago, I can do a retest with the current 2.6.29 and
> see how it behaves.
> 

If CONFIG_NET_DMA=y then available channels will be consumed for 
'public' usage.  I would turn that option off for AVR32 as it hurts 
performance on dma-incoherent archs like ARM.  Async_tx will also 
consume public channels if loaded.  2.6.30 will have the 
CONFIG_ASYNC_TX_DMA option to turn off this allocation... or just set 
DMA_PRIVATE and not worry these :-).

--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/