Roland,
The issue came up during gen1 IPoIB debug.
As far as I was able to track it, header_cache_update() was not called
upon MAC address update, so I had to add an explicit check
in the IPoIB code verifying the data in neighbor->ha and in path->... are consistent
and if not - invalidating the old AH and starting get_path_record flow.
Boris Shpolyansky
Application Engineer
Mellanox Technologies Inc.
2900 Stender Way
Santa Clara, CA 95054
Tel.: (408) 916 0014
Fax: (408) 970 3403
Cell: (408) 834 9365
www.mellanox.com
-----Original Message-----
From: Roland Dreier [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 07, 2005 9:35 AM
To: Michael S. Tsirkin
Cc: [email protected]
Subject: [openib-general] Re: IPoIB question/problem
Michael> Does this analysis make sense? If yes, what would be the
Michael> best way to fix this?
I'm not sure if this could really happen or not. But could we add a
header_cache_update() method to the IPoIB struct net_device to handle this situation if it does occur?
- R.
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
_______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
