mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Komal Shah" <komal.shah802003@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: jes@trained-monkey.org
Subject: gen_pool_destroy(...)?
Date: Tue, 21 Nov 2006 18:29:23 +0200	[thread overview]
Message-ID: <3a5b1be00611210829p75f44b1fu7ba6fde807fb530e@mail.gmail.com> (raw)

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

             reply	other threads:[~2006-11-21 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 16:29 Komal Shah [this message]
2006-12-07 20:53 ` gen_pool_destroy(...)? Jes Sorensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3a5b1be00611210829p75f44b1fu7ba6fde807fb530e@mail.gmail.com \
    --to=komal.shah802003@gmail.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®