linux-kernel - Re: [PATCH V4 1/3] x86: introduce CONFIG_X86_DEV_DMA

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]

Message-ID: <4F87388C.300@zytor.com>
Date:	Thu, 12 Apr 2012 13:18:20 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alessandro Rubini <rubini@...dd.com>
CC:	mingo@...e.hu, akpm@...ux-foundation.org, jbarnes@...tuousgeek.org,
	fujita.tomonori@....ntt.co.jp, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	giancarlo.asnaghi@...com, alan@...ux.intel.com
Subject: Re: [PATCH V4 1/3] x86: introduce CONFIG_X86_DEV_DMA_OPS

On 04/12/2012 01:15 PM, Alessandro Rubini wrote:
> 
> The current approach is using swiotlb and it works pretty well, though
> with a limit of 4MB of swiotlb area.  I've been considering use of the
> DMA zone to this aim: internally I have some half-working thing that
> resuses the ISA DMA zone for our own aims, raising the DMA limit to
> 512MB.
> 
> Do you think the approach may make sense? I use this basic
> thing in Kconfig, to rely on GFP_DMA for the rest:
> 
>   config MAX_DMA_PADDR
>           int
>           default 536870912 if MAX_DMA_PADDR_512M
>           default 16777216
> 
>   config MAX_DMA_PADDR_512M
>           bool
> 
> (actually, we'd benefit from being able to use hex in defaults)
> 
> Is this worth exploring, to possibly submit a patch in this direction?
> 

Not as a compile-time patch.

	-hpa


--
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/