From: Roland Dreier <roland@topspin.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: Advice needed on IP-over-InfiniBand driver
Date: Sun, 19 Sep 2004 21:42:59 -0700 [thread overview]
Message-ID: <523c1dsg8c.fsf@topspin.com> (raw)
In-Reply-To: <20040919140133.60ea3fb3.davem@davemloft.net> (David S. Miller's message of "Sun, 19 Sep 2004 14:01:33 -0700")
David> You probably want to be editing net/ipv4/arp.c and testing
"teaching" not "testing" I assume :)
David> it about Infiniband. Keep neighbour entries in the
David> unresolved stated until both transitions are made:
David> 1) obtain 20 byte address 2) get response from IB subnet
David> manager
David> Only store the destination GID in the neighbour entry, and
David> only mark the neighbour entry as resolved once #2 above
David> completes successfully.
Hmm... it looks like the place you're telling me to hook into is in
arp_process() right before the neigh state gets set to NUD_REACHABLE.
But where should I stick the path information that I get back from the
subnet manager once the query finishes? And how does the path get
passed into the device driver to actually send an skb?
(Sorry to be so dense but I'm afraid my little brain needs things
broken down into bite-sized pieces...)
Thanks,
Roland
next prev parent reply other threads:[~2004-09-20 4:42 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 [this message]
2004-09-28 4:41 ` Roland Dreier
2004-09-28 4:52 ` David S. Miller
2004-09-30 18:41 ` Roland Dreier
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=523c1dsg8c.fsf@topspin.com \
--to=roland@topspin.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
/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).