Skip to contentSkip to conversation

ifIndex allocation

DISCUSSION Sven Schnelle 2 participants 2 messages May 16, 2006

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi List,

investigating a problem with an snmp software for linux, i was wondering why the kernel allocates a new ifindex Number, even if the old one is still available. For example, if i unload a network driver module, and reload it, it has a different ifindex.

Looking at the function dev_new_index (line 2620 in net/core/dev.c) there is a line 'static int ifindex'. Is there any special reason why this variable is static, and the list is not traversed from the beginning, so that the first free ifindex will be used?

Best regards,

Sven.

#1 lore raw
Quoted 1 line · On Tue, 16 May 2006 08:11:01 +0200 "Sven Schnelle" <[email protected]> wrote:

Hi List,

Redirecting to netdev

Quoted 5 lines

investigating a problem with an snmp software for linux, i was wondering why the kernel allocates a new ifindex Number, even if the old one is still available. For example, if i unload a network driver module, and reload it, it has a different ifindex.

Because when you reload the driver it is effectively a completely new object. ifindex is a basically and object id. Ifindices act as soft references so user space can know about a particular network device even if name changes or other operations happen. The reference is soft because the device can disappear. If the application wants to know about device removal it can catch the netlink event.

Quoted 9 lines

Looking at the function dev_new_index (line 2620 in net/core/dev.c) there is a line 'static int ifindex'. Is there any special reason why this variable is static, and the list is not traversed from the beginning, so that the first free ifindex will be used?

Best regards,

Sven.

It is static because no other code should be looking at it. It doesn't retraverse from the start because it doesn't want to reuse an earlier index and confuse an application with a soft reference.