From: tigran@aivazian.fsnet.co.uk
To: lml@beonline.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel / Userspace Data Transfer
Date: Mon, 29 Mar 2004 11:50:08 +0200 (CEST) [thread overview]
Message-ID: <5625455.1080553808079.JavaMail.www@wwinf3002> (raw)
Hello,
One possible solution is to use seq_file API for a /proc file.
I have written a process/system monitor using this method which is about 100
times faster than reading various bits and pieces from /proc by a user application,
so a kernel module is well worth having in this respect. Unfortunately, this software
is not under GPL, but if you do want more information I can send you (or upload
somewhere) a stripped down version which just shows how to use the API
most efficiently and safely.
Kind regards
Tigran
Freeserve AnyTime - HALF PRICE for the first 3 months - Save £7.50 a month
www.freeserve.com/anytime
next reply other threads:[~2004-03-29 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 9:50 tigran [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 4:57 Kernel / Userspace Data Transfer Ross Dickson
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=5625455.1080553808079.JavaMail.www@wwinf3002 \
--to=tigran@aivazian.fsnet.co.uk \
--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.