[Top] [All Lists]

Re: [PATCH 2.6 NET] Device name changing via rtnetlink

To: Thomas Graf <tgraf@xxxxxxx>
Subject: Re: [PATCH 2.6 NET] Device name changing via rtnetlink
From: jamal <hadi@xxxxxxxxxx>
Date: 10 Sep 2004 18:58:02 -0400
Cc: jt@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20040910204348.GL20088@xxxxxxxxxxxxxx>
Organization: jamalopolis
References: <20040910195003.GA13912@xxxxxxxxxxxxxxxxxx> <20040910200644.GJ20088@xxxxxxxxxxxxxx> <20040910201302.GA16556@xxxxxxxxxxxxxxxxxx> <20040910202235.GK20088@xxxxxxxxxxxxxx> <20040910203203.GA17078@xxxxxxxxxxxxxxxxxx> <20040910204348.GL20088@xxxxxxxxxxxxxx>
Reply-to: hadi@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
On Fri, 2004-09-10 at 16:43, Thomas Graf wrote:
> * Jean Tourrilhes <20040910203203.GA17078@xxxxxxxxxxxxxxxxxx> 2004-09-10 13:32
> > On Fri, Sep 10, 2004 at 10:22:35PM +0200, Thomas Graf wrote:
> > > 
> > > 2) Implement NETDEV_CHANGE, I was actually about to implement this
> > >    but it's not directly related to this change and requires the same
> > >    effort by the user space application has refetching the link list.
> > 
> >     Do you have any info on NETDEV_CHANGE, I've got a potential
> > use for it.
> >     (By the way, there are other ways to do it, but if
> > NETDEV_CHANGE is the proposed standard, I might as well use it).
> Currently call_netdevice_notifiers is called and sends out a
> RTM_NEWLINK message with the new interface name to everyone
> wanting to be notified. However, ifi_change is kept to 0
> so far, which means you have to look what has changed yourself. I'm
> not sure if this can be changed without too much troubles but
> I will look into it.

I missed the RTM_NEWLINK part. It is easier to just keep it that way and
make sure it is well documented as so. It may not be trivial (as an
example all the inetdev name attributes change - look at inetdev_event).
So suggestion is to leave it to user space to find more details about
the event.


<Prev in Thread] Current Thread [Next in Thread>