[LU-4989] nodemap: only cancel affected locks on export Created: 01/May/14 Updated: 13/Dec/17 Resolved: 13/Dec/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Andreas Dilger | Assignee: | WC Triage |
| Resolution: | Low Priority | Votes: | 0 |
| Labels: | performance | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 13820 | ||||||||
| Description |
|
Per previous discussion, filing a bug here to track this improvement for the future. When cancelling locks in member_revoke_locks() (added in patch http://review.whamcloud.com/9299) it makes sense to optimize this to only cancel locks on the export that are actuall affected by the change to the idmap (e.g. UID/GID being removed/changed, or node being removed from the idmap or nodemap). |