public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rick Richardson <rickr@mn.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Whats the rvmalloc() story?
Date: Sat, 10 Feb 2001 22:08:08 -0600	[thread overview]
Message-ID: <20010210220808.A18488@mn.rr.com> (raw)


I note that at least 5 device drivers have similar implementations
of rvmalloc()/rvfree() et al:

	ieee1394/video1394.c
	usb/ibmcam.c
	usb/ov511.c
	media/video/bttv-driver.c
	media/video/cpia.c

rvmalloc()/rvfree() are functions that are used to allocate large
amounts of physically non-contiguous kernel virtual memory that will
then be mmap()'ed into a user process.

I just got done writing a driver that needed rvmalloc() in order to do
chip level simulation.  Yank and put to the rescue.

Whats the story behind rvmalloc() et al?  From what I could tell,
about a year ago there were some patches to move rvmalloc() into
vmalloc() as a blessed feature of the kernel.  But it looks to
me like these patches didn't "take".

Is there some other way of doing this now?  If so, does somebody
need to go into these drivers and patch them for the blessed way?
If not, is there some plan in place to bless these functions and
remvoe the code duplication?

-Rick

-- 
Rick Richardson  rickr@mn.rr.com      http://home.mn.rr.com/richardsons/
Twins Cities traffic animations are at http://members.nbci.com/tctraffic/#1
-
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:[~2001-02-11  4:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11  4:08 Rick Richardson [this message]
2001-02-17  7:46 ` Whats the rvmalloc() story? Anton Blanchard
2001-02-17  8:49   ` Rick Richardson
2001-02-17  9:01     ` Anton Blanchard

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=20010210220808.A18488@mn.rr.com \
    --to=rickr@mn.rr.com \
    --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