[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110725.141041.1092565620930748250.davem@davemloft.net>
Date: Mon, 25 Jul 2011 14:10:41 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: roland@...nel.org
Cc: linux-rdma@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH 0/7] More sane neigh infrastructure
From: Roland Dreier <roland@...nel.org>
Date: Mon, 25 Jul 2011 09:34:16 -0700
> So I don't think we can use custom neigh_ops with a new solict method
> the way clip does -- we actually want to let the normal stack do ARP
> or ND, but then extend the process by another message/response step.
> I'm sure this is possible within your scheme but I'm not sure I
> understand what the "right" way is.
So call the normal ARP neigh solicit stuff in your neigh ops, and do
your local stuff there as well.
See if you can make it work.
--
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