On Sun, May 05, 2002 at 10:47:44PM +0300, Oleg Goldshmidt wrote: > Muli Ben-Yehuda <[EMAIL PROTECTED]> writes: > > > The notion of "memory which the kernel module uses" is not very well > > defined, since there are no clear boundaries between the module and > > the kernel (on cannot differentiate between memory used by the > > "base" kernel and memory used by the module). > > Well, a module consists of objects each of which takes up some > memory. Some are static, and the amount of memory they take can (at > least in principle) be determined without even running the module. > Others are dynamic, and thus one would indeed need to hack kmalloc() > and friends to truly monitor that, as you explained and as I had > realized myself - I do not want to muck around with kernel memory > allocation, at least not on the tight project schedule I have.
There's the 'size' field in lsmod output, which appears to be the combined size of the elf sections of the module. > > Can you elaborate further on what you're trying to achieve? > > Well, I don't want to go into describing the heisenbug I am fighting, > and the restrictions I am facing... I would be happy to be able to > make a statement like the one seen in kernel configuration help: "this > will increase the size of your kernel by 65K". That sounds a lot like 'size'? -- The ill-formed Orange Fails to satisfy the eye: http://vipe.technion.ac.il/~mulix/ Segmentation fault. http://syscalltrack.sf.net/ ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
