[Gllug] What does [permanent] mean in an lsmod listing?
John Winters
john at sinodun.org.uk
Wed Jan 4 17:17:34 UTC 2006
On Wed, 2006-01-04 at 17:24 +0000, Richard Jones wrote:
> On Wed, Jan 04, 2006 at 03:02:56PM +0000, John Winters wrote:
> [...]
> > How then I wonder does one decide which of the IDE modules is actually
> > doing the work? I see no point in loading all the others, but hotplug
> > seems to sling them in regardless.
>
> I guess you're running on a _really_ tight system where even 11 pages
> of RAM are important then :-)
>
> > ide_disk 16640 4
> > ide_generic 1408 0 [permanent]
> > via82cxxx 12572 0 [permanent]
>
Sorry - I didn't make myself quite clear. Hotplug seems to be loading
*all* the ide modules, regardless of which one is appropriate and since
they now can't be unloaded they all stay. I didn't include a full
listing last time.
ide_disk 16384 4
ide_generic 1408 0 [permanent]
via82cxxx 12572 0 [permanent]
trm290 4228 0 [permanent]
triflex 3840 0 [permanent]
slc90e66 5504 0 [permanent]
sis5513 14600 0 [permanent]
siimage 11136 0 [permanent]
serverworks 8712 0 [permanent]
sc1200 7040 0 [permanent]
rz1000 2816 0 [permanent]
piix 9860 0 [permanent]
pdc202xx_old 10368 0 [permanent]
opti621 4228 0 [permanent]
ns87415 4296 0 [permanent]
hpt366 17920 0 [permanent]
hpt34x 5120 0 [permanent]
generic 4612 0 [permanent]
cy82c693 4612 0 [permanent]
cs5530 5248 0 [permanent]
cs5520 4736 0 [permanent]
cmd64x 10908 0 [permanent]
atiixp 5776 0 [permanent]
amd74xx 13468 0 [permanent]
alim15x3 11148 0 [permanent]
aec62xx 7040 0 [permanent]
pdc202xx_new 8192 0 [permanent]
ide_core 114912 28
ide_cd,ide_disk,ide_generic,via82cxxx,trm290,triflex,slc90e66,sis5513,siimage,serverworks,sc1200,rz1000,piix,pdc202xx_old,opti621,ns87415,hpt366,hpt34x,generic,cy82c693,cs5530,cs5520,cmd64x,atiixp,amd74xx,alim15x3,aec62xx,pdc202xx_new
It's not so much that I mind them taking up memory, as that I want to
take them out of my kernel configuration so they don't waste time being
compiled each time I re-build my kernel. I remember when I could
compile the kernel for my Dual-PII 450MHz box in just under 5 minutes.
Now a default Sarge kernel takes more like 2 hours on a much faster
system. (Although this slightly old Athlon box seems to have been
greatly encouraged by the installation of a new 300GB hard ATA hard
drive and now out-performs its big brother which uses SATA.)
John
--
Gllug mailing list - Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug
More information about the GLLUG
mailing list