[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090508.162555.193731410.davem@davemloft.net>
Date: Fri, 08 May 2009 16:25:55 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: shemminger@...tta.com
Cc: jpirko@...hat.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, jgarzik@...ox.com,
shemminger@...ux-foundation.org, 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] net: introduce a list of device addresses
dev_addr_list (v6)
From: Stephen Hemminger <shemminger@...tta.com>
Date: Fri, 8 May 2009 16:12:04 -0700
> But the other infrastructure may have same issues (netfilter, etc).
> Just seems like it would be either to have multiple network devices
> so that upper layers could disambiguate easier.
That's quite a heavyweight solution to what is purely
an addressing issue, don't you think?
We can just revert all of that netdev_ops stuff if you
think per-netdev cost doesn't matter :-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists