[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1245151771.9256.3.camel@johannes.local>
Date: Tue, 16 Jun 2009 13:29:31 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Jiri Pirko <jpirko@...hat.com>
Cc: Netdev <netdev@...r.kernel.org>
Subject: Re: [RFC] net: refactor multicast/unicast address list
On Tue, 2009-06-16 at 13:18 +0200, Jiri Pirko wrote:
> Sat, Jun 13, 2009 at 02:28:14PM CEST, johannes@...solutions.net wrote:
> >On Sat, 2009-06-13 at 12:41 +0200, Johannes Berg wrote:
> >> I'm trying to use address lists without netdevs, but as
> >> a first step I thought it would be good to reduce the
> >> amount duplicated code between unicast and multicast
> >> lists.
> >>
> >> After introducing a new 'struct address_list', we can
> >> unify a lot between these. The next step will probably
> >> be exporting the __dev_addr_sync and __dev_addr_unsync
> >> functions so I can use them without a netdev, but this
> >> cleanup can stand on its own.
> >
> >Sorry, this was based against the wrong tree and now I see that in
> >net-next the lists have diverged significantly. Ignore this.
>
> Yes, I've already converted unicast lists to use list_head there. I'm sending
> the patch doing the same for multicast lists soon.
Very nice! After that maybe I'll take a look again at moving things into
a common structure -- I ultimately want to use a multicast list without
a netdev to sync multiple netdevs onto a common multicast list that is
not part of a netdev.
johannes
Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)
Powered by blists - more mailing lists