netdev
[Top] [All Lists]

Re: [PATCH] Add ability to register class interfaces for network class

To: ext Stephen Hemminger <shemminger@xxxxxxxx>
Subject: Re: [PATCH] Add ability to register class interfaces for network class
From: "Teras Timo (EXT-YomiGroup/Helsinki)" <Ext-Timo.Teras@xxxxxxxxx>
Date: Wed, 27 Oct 2004 21:38:04 +0300
Cc: ext ext Christoph Hellwig <hch@xxxxxxxxxxxxx>, davem@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20041027085906.665d0125@xxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <20041026183526.GA23535@xxxxxxxxxxxxxxxxxxxxxx> <20041026184838.GB16621@xxxxxxxxxxxxx> <20041026205239.GA23825@xxxxxxxxxxxxxxxxxxxxxx> <20041027111317.GA27240@xxxxxxxxxxxxx> <417F86F8.6020004@xxxxxxxxx> <20041027085906.665d0125@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
On Wed, Oct 27, 2004 at 08:59:06AM -0700, ext Stephen Hemminger wrote:
> The Ethernet bridge code creates attribute groups in several places
> without additional interfaces.  How hard is it to do:
> 
> int br_sysfs_addbr(struct net_device *dev)
> {
>       struct kobject *brobj = &dev->class_dev.kobj;
>       struct net_bridge *br = netdev_priv(dev);
>       int err;
> 
>       err = sysfs_create_group(brobj, &bridge_group);
>       if (err) {
>               pr_info("%s: can't create group %s/%s\n",
>                       __FUNCTION__, dev->name, bridge_group.name);
>               goto out1;
>       }

This way the problem is that I have to know which devices I will
add the attributes. But the point is to add attributes to
all netdevs.

Using this approach I'd have to enumerate all the interfaces every
now and then.

If I have my class interface I get a callback whenever an
interface is created or deleted and I can automatically add the
attribute to all netdevs.

Cheers,
  Timo

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