Re: Accessing kernel information from a module

[Anand SVR]

Hi,

The module is going to be "memory less" in the sense that it only fetches data
of interest that is already maintained  in the kernel, forms a message
and send it. In terms of memory, may be few skbs might be consumed for
sending the data across for remote monitoring. This is the main
objective of the project.

Yes, for controlling the kernel parameters one may have to add logic,
but I would
presume that is not going to be too complex and big.

Regards
Anand

On 3/21/06, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
> On Tue, 2006-03-21 at 21:39 +0530, Anand SVR wrote:
> > 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.
>
> that is a questionable argument; kernel memory is non-pagable while
> userspace memory is, so for me the tradeoff isn't immediately a clear
> win for doing it in the kernel..
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/