mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Schoeman <justin@suntiger.ee.up.ac.za>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Question on vmalloc() memory management
Date: Tue, 28 Nov 2000 08:49:40 +0200	[thread overview]
Message-ID: <3A235584.B627F510@suntiger.ee.up.ac.za> (raw)

Hi everybody,

I would just like to find out if there is any real reason why there are
no memory management functions for handling vmalloc()ed memory.  If you
have a look at bttv.c, you will see definitions of:

kvirt_to_pa (translate a vmalloc()ed address to a page number)
rvmalloc (malloc and mark as reserved)
rvfree (free and mark as unreserved)

These functions are duplicated (in fact, usually a direct copy), in just
about every video4linux driver (including many as standalone modules),
and some network and sound drivers.

Wouldn't it be a good idea to provide these functions as a standard part
of the mm subsystem of the kernel.  The functions are very small, but
closely related to the vm subsystem - standardising these functions
should reduce the kernel size a little, and also make module development
a little easier (I personally have been caught once or twice by changes
in the mm subsystem breaking the kvirt to phys translation).

Would such a patch be acceptable?  If it is, I will be glad to make a
patch and submit it.

TIA,

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

                 reply	other threads:[~2000-11-28  7:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3A235584.B627F510@suntiger.ee.up.ac.za \
    --to=justin@suntiger.ee.up.ac.za \
    --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®