Skip to contentSkip to conversation

For what stand's __initdata, __devinit etc. ?

Question René Bolldorf 4 participants 5 messages Jan 12, 2010 – Jan 13, 2010

lore
Share & tools
lore
#0 lore raw

Hi,
Do we really need this?
It will be nice if someone can me explain this.

Thx in advance.

René

#1 lore raw
Quoted 3 lines · René Bolldorf

Hi,
Do we really need this?
It will be nice if someone can me explain this.

http://kernelnewbies.org/FAQ/InitExitMacros

Signature · 4 lines
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 2010-01-13 00:42 schrieb Henrique de Moraes Holschuh:

Quoted 6 lines · René Bolldorf
Quoted 3 lines

Hi,
Do we really need this?
It will be nice if someone can me explain this.

http://kernelnewbies.org/FAQ/InitExitMacros

That's far from complete. It does not, for example, mention __devinit.

- --
Tilman Schmidt E-Mail: [email protected]
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite) -----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktNsOMACgkQQ3+did9BuFtfrwCfUO+z1SWLRs97+lrfp6FjC61a dzwAnR02pQ+qAdSN58YEh1kL8BwoRwqz
=z9Hb
-----END PGP SIGNATURE-----

#3 lore raw
Quoted 9 lines · Tilman Schmidt

Am 2010-01-13 00:42 schrieb Henrique de Moraes Holschuh:

Quoted 6 lines · René Bolldorf
Quoted 3 lines

Hi,
Do we really need this?
It will be nice if someone can me explain this.

http://kernelnewbies.org/FAQ/InitExitMacros

That's far from complete. It does not, for example, mention __devinit.

This wiki contains also somewhat misleadingly worded text: "But why must you use these macros ?" This should read: "But why would you want to use these macros?"

Answer: They are a micro-optimization which allows the kernel to free memory that was occupied by this code at some point, because that code won't be used after that point anymore. (In case of exit macros: These are hints to discard some code from a build in case of certain kernel configurations.) These macros only affect code which is statically linked into the kernel.

Some macros, like for example __devinit, have so obscure uses and marginal benefits that a normal developer should not bother about them. __devinit in particular does not have any effect at all --- except if CONFIG_HOTPLUG is not defined. This may happen in configurations for embedded systems. But the majority of device drivers that you can find in the kernel tree are irrelevant (i.e. configured off) on such systems anyway.

Some more information on these macros can be found in Corbet, Rubini,
Kroah-Hartman: Linux Device Drivers, 3rd edition a.k.a. LDD3, which is also gratis available on the Web.

Signature · 3 lines
Stefan Richter
-=====-==-=- ---= -==-=
http://arcgraph.de/sr/
#4 lore raw
Quoted 30 lines · Stefan Richter
Quoted 9 lines · Tilman Schmidt

Am 2010-01-13 00:42 schrieb Henrique de Moraes Holschuh:

Quoted 6 lines · René Bolldorf
Quoted 3 lines

Hi,
Do we really need this?
It will be nice if someone can me explain this.

http://kernelnewbies.org/FAQ/InitExitMacros

That's far from complete. It does not, for example, mention __devinit.

This wiki contains also somewhat misleadingly worded text: "But why must you use these macros ?" This should read: "But why would you want to use these macros?"

Answer: They are a micro-optimization which allows the kernel to free memory that was occupied by this code at some point, because that code won't be used after that point anymore. (In case of exit macros: These are hints to discard some code from a build in case of certain kernel configurations.) These macros only affect code which is statically linked into the kernel.

Some macros, like for example __devinit, have so obscure uses and marginal benefits that a normal developer should not bother about them. __devinit in particular does not have any effect at all --- except if CONFIG_HOTPLUG is not defined. This may happen in configurations for embedded systems. But the majority of device drivers that you can find in the kernel tree are irrelevant (i.e. configured off) on such systems anyway.

Quoted 3 lines

Some more information on these macros can be found in Corbet, Rubini,
Kroah-Hartman: Linux Device Drivers, 3rd edition a.k.a. LDD3, which is also gratis available on the Web.

Thanks @all :-)