linux-kernel - gen_pool

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-next>] [day] [month] [year] [list]

Date:	Tue, 21 Nov 2006 18:29:23 +0200
From:	"Komal Shah" <komal.shah802003@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	jes@...ined-monkey.org
Subject: gen_pool_destroy(...)?

Hi,

Why we don't have gen_pool_destroy(...) like mempool_destroy(...)? As
of now I can only see the application of genalloc function in
ia64/uncached.c file only.

Reason, why I am asking is, that I have dual-core embedded processor
(ARM11-ARM7), ARM11 being the master and the bridge between the two
has to manage the customized ARM7-MMU (which offers me 4GB of virtual
address space, but in application/driver, we would like to use only
2GB).

So, before mapping any user-space allocated/kernel allocated buffer to
ARM7-MMU so that it can be visible there, I want to check that Is
there any enough space left in that ARM7 virtual address space, if
yes, I want allow that virtual address to be used for mapping the
buffer.

So, use of it might go like this...

rsvpool =  gen_pool_create(PAGE_SHIFT, -1)..

gen_pool_add(rsvpool, addr, SZ_2G, -1);

....then alloc/check the space as requested by the user/kernel buffer..eg. SZ_4K

gen_pool_alloc(rsvpool, SZ_4K);

Now, each reserved pool allocation should also keep track of if it is
really mapped to ARM7 or not....

but finally when driver unloads, it should delete the pool...with
something like gen_pool_destroy(...) isn't it?

-- 
---Komal Shah
http://komalshah.blogspot.com
-
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/