summaryrefslogtreecommitdiffstats
path: root/firmware/e100
diff options
context:
space:
mode:
authorSteven Whitehouse <swhiteho@redhat.com>2010-09-03 10:07:48 -0500
committerDavid Teigland <teigland@redhat.com>2010-09-03 10:10:47 -0500
commit314dd2a05340fffbe217c5e40ec6c3bd1d07bf89 (patch)
treec4e5cf876ed951e47e7fad8bef0c69ea5df0c7dd /firmware/e100
parent2bfc96a127bc1cc94d26bfaa40159966064f9c8c (diff)
downloadop-kernel-dev-314dd2a05340fffbe217c5e40ec6c3bd1d07bf89.zip
op-kernel-dev-314dd2a05340fffbe217c5e40ec6c3bd1d07bf89.tar.gz
dlm: Don't send callback to node making lock request when "try 1cb" fails
When converting a lock, an lkb is in the granted state and also being used to request a new state. In the case that the conversion was a "try 1cb" type which has failed, and if the new state was incompatible with the old state, a callback was being generated to the requesting node. This is incorrect as callbacks should only be sent to all the other nodes holding blocking locks. The requesting node should receive the normal (failed) response to its "try 1cb" conversion request only. This was discovered while debugging a performance problem on GFS2, however this fix also speeds up GFS as well. In the GFS2 case the performance gain is over 10x for cases of write activity to an inode whose glock is cached on another, idle (wrt that glock) node. (comment added, dct) Signed-off-by: Steven Whitehouse <swhiteho@redhat.com> Tested-by: Abhijith Das <adas@redhat.com> Signed-off-by: David Teigland <teigland@redhat.com>
Diffstat (limited to 'firmware/e100')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud