From: "Anand SVR" <anand.svr@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accessing kernel information from a module
Date: Tue, 21 Mar 2006 21:39:08 +0530 [thread overview]
Message-ID: <48a4d13c0603210809n681c3594mcdb41b7578a36dbd@mail.gmail.com> (raw)
In-Reply-To: <48a4d13c0603210338s4cd1f120k80e1bbe6ac70669c@mail.gmail.com>
Hi,
I forgot to mention one more context. In the embedded environment where
one is memory constrained, the lightweight and low memory foot-print
module I am referring to becomes relevant. In addition, since it is
highly reliable, and remotely manageable as listed below I feel it is
worth pursuing.
Thanks for your time.
Regards
Anand
On 3/21/06, Anand SVR <anand.svr@gmail.com> wrote:
> Hi,
>
> The code is not yet ready :) I have a basic version that gives part of
> memory statistics.
>
> Why I want to do it in kernel ? Following are the reasons.
>
> - Not all the information is available to the user space. There may be
> situations where kernel developers, carrier grade server mainatainers,
> and the like might want to access some internal run-time information
> for debugging, fine-tuning and so on.
>
> - Keep it light weight, and least intrusive to the run-time behavior
> of the system. No need for tcp/udp socket communication.
>
> - There could be impending catastrophic situations where in kernel
> cannot schedule user level processes, perhaps due to lack of memory or
> whatever.
>
> - Ability for the remote node to change/control certain kernel
> parameters by interacting with the module. This paves way for both
> diagnosing and controlling kernel.
>
> Regards
> Anand
>
> On 3/21/06, Arjan van de Ven <arjan@infradead.org> wrote:
> > On Tue, 2006-03-21 at 16:32 +0530, Anand SVR wrote:
> > > Hi,
> > >
> > > I am in the process of writing a module that collects kernel
> > > information of various kernel subsytems and pass this on to a remote
> > > monitoring/management node. The information could be statistical data
> > > maintained in data structures of memory, process, network and so on.
> > > Or it could be any kernel variables that are of interest.
> >
> > you forgot to attach your source code ;)
> >
> > > Is there a way of accessing proc information from the module ?
> >
> > eh why on earth is your code in the kernel then? Shouldn't your code be
> > in userspace if you want to send such information to a remote system???
> >
> >
> >
>
next prev parent reply other threads:[~2006-03-21 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 11:02 Anand SVR
2006-03-21 11:12 ` Arjan van de Ven
[not found] ` <48a4d13c0603210338s4cd1f120k80e1bbe6ac70669c@mail.gmail.com>
2006-03-21 11:40 ` Fwd: " Anand SVR
2006-03-21 16:09 ` Anand SVR [this message]
2006-03-22 1:36 ` Sumit Narayan
[not found] ` <1142958503.3077.98.camel@laptopd505.fenrus.org>
2006-03-22 6:09 ` Anand SVR
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=48a4d13c0603210809n681c3594mcdb41b7578a36dbd@mail.gmail.com \
--to=anand.svr@gmail.com \
--cc=arjan@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®