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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 05 Nov 2006 21:19:24 -0500
From:	Phillip Susi <psusi@....rr.com>
To:	Jun Sun <jsun@...sun.net>
CC:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Can Linux live without DMA zone?

Jun Sun wrote:
> Perhaps a better solution is to 
> 
> 1. get rid of DMA zone
> 
> 2. have another alloc funciton (e.g., kmalloc_range()) which takes an
>    extra pair of parameters to indicate the desired range for the
>    allocated memory.  Most DMA buffers are allocated during start-up.
>    So the alloc operations should generally be successful.
> 
> 3. convert drivers over to use the new function.
> 
> Cheers.
> 
> Jun
>    are allocated at start-up time.

That is what I was thinking.  You don't need lots of separate pools, you 
just need the standard allocator to prefer higher addresses, and then 
the bounce routines need to simply check if the existing user buffer 
happens to already be within the area the hardware can address ( which 
it often will be ), and if not, copy the data to pages allocated in 
lower memory.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ