From: "Christopher Friesen" <cfriesen@nortel.com>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Sharing memory between kernel and user space
Date: Tue, 30 May 2006 17:21:14 -0600 [thread overview]
Message-ID: <447CD36A.1040201@nortel.com> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA0012B331D@chicken.machinevisionproducts.com>
Brian D. McGrew wrote:
> I'm using the 2.6.16.16 kernel. Is there any chance that I could
> trouble you for a snippet of code to do that? I've tried every
> combination I can think of.
You could try looking at how /dev/kmem does it.
Also, be aware that the size of "unsigned long" can vary between the
kernel and userspace if you have a 64-bit machine.
Chris
next prev parent reply other threads:[~2006-05-30 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 22:53 Sharing memory between kernel and user space Brian D. McGrew
2006-05-30 23:21 ` Christopher Friesen [this message]
2006-05-31 12:33 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 20:38 Brian D. McGrew
2006-05-31 0:09 Brian D. McGrew
2006-05-30 22:32 Brian D. McGrew
2006-05-30 22:46 ` H. Peter Anvin
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=447CD36A.1040201@nortel.com \
--to=cfriesen@nortel.com \
--cc=brian@visionpro.com \
--cc=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.