From: Stephen Hemminger <shemminger@osdl.org>
To: "Sven Schnelle" <svens@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: ifIndex allocation
Date: Tue, 16 May 2006 09:38:30 -0700 [thread overview]
Message-ID: <20060516093830.5e755993@localhost.localdomain> (raw)
In-Reply-To: <86r72uh53e.fsf@deprecated.bitebene.org>
On Tue, 16 May 2006 08:11:01 +0200
"Sven Schnelle" <svens@gmx.de> wrote:
> Hi List,
Redirecting to netdev
>
> 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.
> 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.
parent reply other threads:[~2006-05-16 16:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86r72uh53e.fsf@deprecated.bitebene.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060516093830.5e755993@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=svens@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).