lkml.org 
[lkml]   [2009]   [Apr]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 3/4] net: bridge: use device address list instead of dev_addr
Mon, Apr 13, 2009 at 04:54:00PM CEST, shemminger@vyatta.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.


\
 
 \ /
  Last update: 2009-04-14 12:19    [W:0.130 / U:0.748 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site