From: Roland Dreier <roland@topspin.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com, openib-general@openib.org
Subject: Re: Advice needed on IP-over-InfiniBand driver
Date: Thu, 30 Sep 2004 11:41:07 -0700 [thread overview]
Message-ID: <521xgj1tx8.fsf@topspin.com> (raw)
In-Reply-To: <20040927215244.697aaa02.davem@davemloft.net> (David S. Miller's message of "Mon, 27 Sep 2004 21:52:44 -0700")
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
next prev parent reply other threads:[~2004-09-30 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 4:08 Advice needed on IP-over-InfiniBand driver Roland Dreier
2004-09-19 21:01 ` David S. Miller
2004-09-19 21:19 ` jamal
2004-09-20 2:34 ` David S. Miller
2004-09-20 4:51 ` Roland Dreier
2004-09-20 4:49 ` Roland Dreier
2004-09-21 11:35 ` jamal
2004-09-21 15:23 ` Roland Dreier
2004-09-20 4:42 ` Roland Dreier
2004-09-28 4:41 ` Roland Dreier
2004-09-28 4:52 ` David S. Miller
2004-09-30 18:41 ` Roland Dreier [this message]
2004-09-30 21:21 ` David Stevens
2004-09-30 21:48 ` Roland Dreier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521xgj1tx8.fsf@topspin.com \
--to=roland@topspin.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=openib-general@openib.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).