linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark_H_Johnson@Raytheon.com
To: linux-mm@kvack.org
Cc: James_P_Cassidy@Raytheon.com
Subject: Physical address of a user virtual address
Date: Mon, 29 Oct 2001 18:42:51 -0600	[thread overview]
Message-ID: <OF59D35C34.54785967-ON86256AF5.0002C7E7@hou.us.ray.com> (raw)

We have an application where we will be...
 - using mlockall() to lock the application into physical memory
 - communicating to / from other systems using an interface similar to
shared memory
 - most of the other systems run Linux - we have a device driver to handle
that case (they exchange information so the operation is "safe")
 - but one of the other systems does not have an operating system - just
our code

For the system with our code in it, we need the physical address of a
region in the user's virtual address space. We are aware of the problems
with memory fragmentation and would be probing several addresses (at 4
Kbyte boundaries) to compute the base address & lengths of each contiguous
region.

We can't seem to find any "easy" way (e.g., call a function) that converts
an address in the virtual address space of an application to the physical
address. The book "Linux Device Drivers" basically tells us to walk the
page tables. From that, we think we must create a driver or kernel module
to get access to the proper variables and functions. That looks like a lot
of work for something that sounds simple.

Has someone already solved this done this and can point us to some code
that implements this?

Is there a better way to solve this problem?

Thanks.
--Mark H Johnson
  <mailto:Mark_H_Johnson@raytheon.com>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

             reply	other threads:[~2001-10-30  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  0:42 Mark_H_Johnson [this message]
2001-10-30 18:17 ` Timur Tabi
2001-11-01 14:08 ` Stephen C. Tweedie

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=OF59D35C34.54785967-ON86256AF5.0002C7E7@hou.us.ray.com \
    --to=mark_h_johnson@raytheon.com \
    --cc=James_P_Cassidy@Raytheon.com \
    --cc=linux-mm@kvack.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