Re: Accessing kernel information from a module

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <[email protected]> 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 <[email protected]> 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???
> >
> >
> >
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux