netdev
[Top] [All Lists]

Re: Advice needed on IP-over-InfiniBand driver

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: Advice needed on IP-over-InfiniBand driver
From: Roland Dreier <roland@xxxxxxxxxxx>
Date: Thu, 30 Sep 2004 11:41:07 -0700
Cc: netdev@xxxxxxxxxxx, openib-general@xxxxxxxxxx
In-reply-to: <20040927215244.697aaa02.davem@davemloft.net> (David S. Miller's message of "Mon, 27 Sep 2004 21:52:44 -0700")
References: <52fz5esxx6.fsf@topspin.com> <20040919140133.60ea3fb3.davem@davemloft.net> <52r7onc8ev.fsf@topspin.com> <20040927215244.697aaa02.davem@davemloft.net>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux)
    David> I think you might learn something by having a look at what
    David> net/atm/clip.c is doing, it creates it's own neighbour
    David> layer for CLIP ATM neighbours.  It is in a similar boat to
    David> your IPoIB stuff.

Thanks, this suggestion was very helpful.  I think I'm making
progress.  Now I know my next question :)

CLIP ATM is a little different from IPoIB in that it completely
replaces the ARP layer with its own ARP daemon.  For IPoIB I don't
want to reinvent the ARP and ND code -- I just want to add a secondary
lookup after the response comes back.  I think I have an idea of how
to do that and then stash the information in the struct neighbour, so
that my hard_start_xmit method can get it from skb->dst (ala clip.c).

However, it seems that broadcast ARP packets have skb->dst == NULL.
Is it safe for me to assume that packets with skb->dst == NULL are
broadcast packets?  Will multicast packets have a non-NULL dst?

Thanks,
  Roland

<Prev in Thread] Current Thread [Next in Thread>