netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Mason <jdmason@us.ibm.com>
To: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
Cc: netdev@oss.sgi.com, davem@davemloft.net
Subject: Re: [PATCH] [BRIDGE] Set features based on slave's ones (was Ethernet Bridging: Enable Hardware Checksumming)
Date: Thu, 19 May 2005 16:40:15 -0500	[thread overview]
Message-ID: <20050519214015.GA19961@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0505191654400.24043@webhosting.rdsbv.ro>

On Thu, May 19, 2005 at 06:28:26PM +0300, Catalin(ux aka Dino) BOIE wrote:
> Hello!
> 
> The attached patch, makes the bridge to select features (almost all) only 
> if _all_ devices supports them.
> The patch was tested (create a bridge, add an interface, remove the 
> interface and always check features flags).
> 
> What do you think?
> 
> Signed-off-by: Catalin(ux aka Dino) BOIE <catab at umbrella.ro>
> ---
> Catalin(ux aka Dino) BOIE
> catab at deuroconsult.ro
> http://kernel.umbrella.ro/

> --- bridge1/net/bridge/br_private.h	2005-03-02 09:37:50.000000000 +0200
> +++ linux/net/bridge/br_private.h	2005-05-19 18:00:05.000000000 +0300
> @@ -27,6 +27,10 @@
>  #define BR_PORT_BITS	10
>  #define BR_MAX_PORTS	(1<<BR_PORT_BITS)
>  
> +#define BR_FEAT_MASK	(NETIF_F_HW_CSUM | NETIF_F_SG \
> +			| NETIF_F_FRAGLIST | NETIF_F_IP_CSUM \
> +			| NETIF_F_HIGHDMA | NETIF_F_TSO)
> +
>  typedef struct bridge_id bridge_id;
>  typedef struct mac_addr mac_addr;
>  typedef __u16 port_id;
> --- bridge1/net/bridge/br_device.c	2005-03-02 09:37:30.000000000 +0200
> +++ linux/net/bridge/br_device.c	2005-05-19 17:14:21.000000000 +0300
> @@ -107,4 +107,5 @@ void br_dev_setup(struct net_device *dev
>  	dev->tx_queue_len = 0;
>  	dev->set_mac_address = NULL;
>  	dev->priv_flags = IFF_EBRIDGE;
> +	dev->features = BR_FEAT_MASK;
>  }
> --- bridge1/net/bridge/br_if.c	2005-03-02 09:38:33.000000000 +0200
> +++ linux/net/bridge/br_if.c	2005-05-19 18:21:39.000000000 +0300
> @@ -314,6 +314,27 @@ int br_min_mtu(const struct net_bridge *
>  	return mtu;
>  }
>  
> +/*
> + * If slave device (@dev) doesn't support special features,
> + * turn them off globally.
> + */
> +static inline void br_features_change(struct net_bridge *br, struct net_device *dev)
> +{
> +	br->dev->features &= dev->features | ~BR_FEAT_MASK;

~BR_FEAT_MASK isn't necessary. Either you wanted to do an '&' just
before it, so that BR_FEAT_MASK features are the only ones that you want
or you are enabling features that aren't necessarily supported by the
adapter/driver (like LLTX and HW_VLAN stuff).

> +}
> +
> +/*
> + * Recomputes features using slave's features
> + */
> +static void br_features_recompute(struct net_bridge *br)
> +{
> +	struct net_bridge_port *p;
> +
> +	br->dev->features |= BR_FEAT_MASK;

The OR is not needed.  Just re-initialize features to BR_FEAT_MASK and
everything will take case of itself.

> +	list_for_each_entry(p, &br->port_list, list)
> +		br_features_change(br, p->dev);
> +}
> +
>  /* called with RTNL */
>  int br_add_if(struct net_bridge *br, struct net_device *dev)
>  {
> @@ -332,9 +353,10 @@ int br_add_if(struct net_bridge *br, str
>  	if (IS_ERR(p = new_nbp(br, dev, br_initial_port_cost(dev))))
>  		return PTR_ERR(p);
>  
> +	br_features_change(br, dev);
> +
>   	if ((err = br_fdb_insert(br, p, dev->dev_addr, 1)))
>  		destroy_nbp(p);
> - 
>  	else if ((err = br_sysfs_addif(p)))
>  		del_nbp(p);
>  	else {
> @@ -368,6 +390,7 @@ int br_del_if(struct net_bridge *br, str
>  
>  	spin_lock_bh(&br->lock);
>  	br_stp_recalculate_bridge_id(br);
> +	br_features_recompute(br);
>  	spin_unlock_bh(&br->lock);
>  
>  	return 0;

  parent reply	other threads:[~2005-05-19 21:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 15:28 [PATCH] [BRIDGE] Set features based on slave's ones (was Ethernet Bridging: Enable Hardware Checksumming) Catalin(ux aka Dino) BOIE
2005-05-19 15:59 ` Nivedita Singhvi
2005-05-19 18:52   ` [PATCH] [BRIDGE] Set features based on slave's ones David S. Miller
2005-05-19 16:06 ` [PATCH] [BRIDGE] Set features based on slave's ones (was Ethernet Bridging: Enable Hardware Checksumming) Jon Mason
2005-05-19 17:22   ` Catalin(ux aka Dino) BOIE
2005-05-19 17:47     ` Jon Mason
2005-05-19 18:58       ` [PATCH] [BRIDGE] Set features based on slave's ones David S. Miller
2005-05-19 19:07         ` Jon Mason
2005-05-19 19:00     ` [PATCH] [BRIDGE] Set features based on slave's ones (was Ethernet Bridging: Enable Hardware Checksumming) Jon Mason
2005-05-19 19:21       ` [PATCH] [BRIDGE] Set features based on slave's ones David S. Miller
2005-05-19 20:20         ` Jon Mason
2005-05-19 18:53   ` David S. Miller
2005-05-19 20:39 ` [PATCH] [BRIDGE] Set features based on slave's ones (was Ethernet Bridging: Enable Hardware Checksumming) Stephen Hemminger
2005-05-19 21:20 ` Stephen Hemminger
2005-05-19 21:40 ` Jon Mason [this message]
2005-05-20  6:07   ` Catalin(ux aka Dino) BOIE
2005-05-20 18:54     ` Jon Mason
2005-05-23  9:39       ` Catalin(ux aka Dino) BOIE
2005-05-23  9:40       ` Catalin(ux aka Dino) BOIE
2005-05-23 19:14         ` Jon Mason

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=20050519214015.GA19961@us.ibm.com \
    --to=jdmason@us.ibm.com \
    --cc=davem@davemloft.net \
    --cc=netdev@oss.sgi.com \
    --cc=util@deuroconsult.ro \
    /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).