All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: lml@beonline.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel / Userspace Data Transfer
Date: Sun, 28 Mar 2004 22:37:23 -0500	[thread overview]
Message-ID: <406799F3.1020508@opersys.com> (raw)
In-Reply-To: <1080528430.40678e2e9eb3a@www.beonline.com.au>


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?

relayfs has been designed with this type of requirements in mind:
http://www.opersys.com/relayfs/index.html

Karim
-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546


  reply	other threads:[~2004-03-29  3:31 UTC|newest]

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

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=406799F3.1020508@opersys.com \
    --to=karim@opersys.com \
    --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.