[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090414101512.GA3999@psychotron.englab.brq.redhat.com>
Date: Tue, 14 Apr 2009 12:15:13 +0200
From: Jiri Pirko <jpirko@...hat.com>
To: Stephen Hemminger <shemminger@...tta.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
jgarzik@...ox.com, davem@...emloft.net,
bridge@...ts.linux-foundation.org, fubar@...ibm.com,
bonding-devel@...ts.sourceforge.net, kaber@...sh.net,
mschmidt@...hat.com, dada1@...mosbay.com, ivecera@...hat.com
Subject: Re: [PATCH 3/4] net: bridge: use device address list instead of
dev_addr
Mon, Apr 13, 2009 at 04:54:00PM CEST, shemminger@...tta.com wrote:
>> +static int another_port_has_addr(const struct net_bridge_port *p,
>> + struct net_bridge_fdb_entry *f)
>> +{
>> + struct net_bridge *br = p->br;
>> + struct net_bridge_port *op;
>> +
>> + list_for_each_entry(op, &br->port_list, list) {
>> + if (op != p && is_dev_addr(op->dev, f->addr.addr)) {
>> + f->dst = op;
>> + return 1;
>> + }
>> + }
>> + return 0;
>> +}
>
>Forwarding database is hot path, people sometimes run lots of devices
>on single bridge, doesn't this scale worse?
>
This only puts the original loop code to the function, so if compiler decides to
inline this there might be no difference.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists