All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Dickson <ross@datscreative.com.au>
To: lml@beonline.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel / Userspace Data Transfer
Date: Mon, 29 Mar 2004 14:57:10 +1000	[thread overview]
Message-ID: <200403291457.10653.ross@datscreative.com.au> (raw)

lml@beonline.com.au wrote: 
 > I have a set of counters in a Kernel module that i want to export to a 
 > userspace application. I originally decided to use a /proc entry and parse 
 > the output whenever the userspace application needed this data, however, 
 > i need more than the 4096 that is allowed in /proc and i'm not too keen 
 > on parsing large chunks of text anyway. 
 > 
 > What i would like to do is copy these slabs of text from the kernel to my 
 > userspace application (whenever the application requests it). I've seen the 
 > 'copy_to_user' function and it looks usefull, but have no idea where to start 
 > or how to use it :-/ 
 > 
 > Can someone provide and example or point me in the right direction? Or is there 
 > a better place to ask this question? 
 
Here is a good starter on-line reference
http://www.faqs.org/docs/kernel/
Relevant page
http://www.faqs.org/docs/kernel/x848.html
or as pdf
http://www.tldp.org/LDP/lkmpg/lkmpg.pdf

There is also mbuff that maps shared memory between kernel and user space.
It is pretty easy to use.
http://sourceforge.net/projects/mbuff/

Regards
Ross.

             reply	other threads:[~2004-03-29  4:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29  4:57 Ross Dickson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-29  9:50 Kernel / Userspace Data Transfer tigran
2004-03-29  2:47 lml
2004-03-29  3:37 ` Karim Yaghmour
2004-03-29  9:45   ` Pavel Mironchik
2004-03-29  9:09     ` Emmanuel Fleury
2004-03-29 14:29     ` Karim Yaghmour

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=200403291457.10653.ross@datscreative.com.au \
    --to=ross@datscreative.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lml@beonline.com.au \
    /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.