From: Sean Hefty Date: Mon, 15 Nov 2010 20:08:46 +0000 (-0800) Subject: new X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=0ffffce6df76d3abf3897a82ac22b3c37d77d1e5;p=~shefty%2Fibacm.git new --- diff --git a/meta b/meta index 38209e3..6295c5b 100644 --- a/meta +++ b/meta @@ -1,8 +1,9 @@ Version: 1 -Previous: 12e5a68361af88fde30e3299870ac0f24a8279e0 -Head: 88d1bcda7ee4d64fe55e1e639cd485422a30c23b +Previous: 76b1560498425d0e0142ac5b331bdf6c6eebe6f5 +Head: b132c3874f32b66cb122e46bb03bd22f3c8bcd0a Applied: logging: 88d1bcda7ee4d64fe55e1e639cd485422a30c23b + acm_snoop: b132c3874f32b66cb122e46bb03bd22f3c8bcd0a Unapplied: loopback: 8c3473645ff2d6097b6a9c351a726ea48c1d8165 Hidden: diff --git a/patches/acm_snoop b/patches/acm_snoop new file mode 100644 index 0000000..dbce534 --- /dev/null +++ b/patches/acm_snoop @@ -0,0 +1,29 @@ +Bottom: d1d96503c5833062d50818f5ab44f42d2432089a +Top: d1d96503c5833062d50818f5ab44f42d2432089a +Author: Sean Hefty +Date: 2010-11-15 12:08:46 -0800 + +ibacm: fix issuing SA query after recording address + +ACM has two ways that it can complete address resolution. The +first is to receive a response to an addres resolution query. +The second is to receive a multicast message carrying an address +resolution request. In the second case, the address request +may be between two other nodes. + +When this occurs, ACM will record the address information of +the source of the multicast message. However, it's possible +for ACM to be in the process of trying to resolve that address. +After it records the address, it must see if there's an +outstanding request against that address, so that it can kick +off route resolution. + +This fixes an issue where ACM will hang resolving addresses +found during scale-up testing. + +Signed-off-by: Sean Hefty + + +--- + +